Notice
Recent Posts
Recent Comments
Link
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
Tags
- Terraform GKE
- AWS session manager
- ACM
- S3
- 벨로그
- Decapsulation
- AWS client VPN 인증서
- Encapsulation
- client vpn
- client vpn 인증서
- java s3 400
- 비공개 GKE
- velog
- s3 upload 400
- 비공개 GKE autorized
- 프라이빗 EC2 접속
- Session Manager
- 독서노트
- TCP/IP
- 엔지니어블로그
- 문과남자의 과학공부
- 티스토리
- ACM 도메인
- Terrafrom GCP
- 테라폼 private GKE
- aws
- Terraform GCP GKE
- AWS private EC2
Archives
- Today
- Total
망지로그
CKA - ingress 본문
https://kubernetes.io/docs/concepts/services-networking/ingress/#path-types
Ingress
Make your HTTP (or HTTPS) network service available using a protocol-aware configuration mechanism, that understands web concepts like URIs, hostnames, paths, and more. The Ingress concept lets you map traffic to different backends based on rules you defin
kubernetes.io
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: simple-fanout-example
spec:
rules:
- host: foo.bar.com
http:
paths:
- path: /foo
pathType: Prefix
backend:
service:
name: service1
port:
number: 4200
- path: /bar
pathType: Prefix
backend:
service:
name: service2
port:
number: 8080
여기서 port number는 svc의 포트를 넣어줄 것 ! pod 포트가 아닙니다.
'Kubernetes' 카테고리의 다른 글
CKA -trouble shooting (0) | 2024.07.04 |
---|---|
CKA- kubeadm (0) | 2024.07.04 |
CKA - core DNS in k8s (0) | 2024.07.03 |
CKA - service networking (0) | 2024.07.03 |
CKA - Networking weave (0) | 2024.07.03 |