# 실습
## Ingress-NGINX Controller
### Introduction
1. Helm 차트 리포지토리 추가
```
{
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
}
```
2. Ingress-NGINX Controller 설치
```
helm install ingress-nginx ingress-nginx/ingress-nginx -n kube-system \
--set controller.service.annotations.service\\.beta\\.kubernetes\\.io/aws-load-balancer-type=nlb
```
3. 배포된 구성요소 확인
```
kubectl -n kube-system get all -l app.kubernetes.io/name=ingress-nginx
```
4. 생성된 Service 확인
```
kubectl -n kube-system get svc ingress-nginx-controller
```
5. 생성된 NLB 상세 내용 확인
```
aws elbv2 describe-load-balancers --names \
$(kubectl -n kube-system get svc ingress-nginx-controller \
-o jsonpath='{.status.loadBalancer.ingress[0].hostname}' \
| grep -o -E '^[a-z0-9]+' ) --no-cli-pager
```
6. 웹 브라우저를 열고 Service의 External IP 주소로 접속 - *아래의 명령어로 주소 확인 가능*
```
kubectl -n kube-system get svc ingress-nginx-controller \
-o jsonpath='{.status.loadBalancer.ingress[0].hostname}{"\n"}'
```
7. 생성된 NGINX Ingress Controller Pod에서 실행중인 프로세스 확인
```
kubectl -n kube-system exec deploy/ingress-nginx-controller -- \
ps aux
```
8. NGINX 설정 파일 리뷰
```
kubectl -n kube-system exec deploy/ingress-nginx-controller -- \
cat /etc/nginx/nginx.conf
```
9. 생성된 NLB 주소로 접속했을때 404 Not Found가 나오는 이유 확인
```
kubectl -n kube-system exec deploy/ingress-nginx-controller -- \
cat /etc/nginx/nginx.conf | grep 404 -B 9 -A 2
```
### Virtual hosting
1. Deployment 생성
```
{
kubectl create deployment nginx --image=nginx --port=80
kubectl create deployment httpd --image=httpd --port=80
}
```
2. Service 생성
```
{
kubectl expose deploy nginx
kubectl expose deploy httpd
}
```
3. 생성된 Service 확인
```
kubectl get svc -l app
```
4. Ingress 생성
```
cat <
```
cat < ca.json < ca-config.json < mycompany-csr.json <
22. Ingress 수정
```
cat <
33. AWS Load Balancer Controller로 Ingress 생성할때 요구되는 파라미터 및 기본값 확인 -
34. Ingress 수정
```
cat <
{"type":"fixed-response","fixedResponseConfig":{"contentType":"text/plain","statusCode":"404","messageBody":"Not Found"}}
spec:
ingressClassName: alb
defaultBackend:
service:
name: response-404
port:
name: use-annotation
EOF
```
2. 생성된 Ingress 확인
```
kubectl get ing my-service
```
3. 위에서 생성한 Ingress에 발생한 Event 확인
```
kubectl describe ingress my-service
```
4. AWS Load Balancer Controller 로그 확인
```
kubectl -n kube-system logs deploy/aws-load-balancer-controller --tail 15
```
5. 아래의 명령어를 실행해서 생성된 ALB 엔드포인트를 확인하고 웹브라우저를 통해서 접근이 되는지 확인
```
echo $(kubectl get ing my-service -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}')
```
6. Product 서비스 배포
```
cat <<'EOF' | kubectl apply -f -
apiVersion: apps/v1
kind: Deployment
metadata:
name: product
labels:
app: product
spec:
selector:
matchLabels:
app: product
template:
metadata:
labels:
app: product
spec:
containers:
- name: product
image: nginx
ports:
- containerPort: 80
volumeMounts:
- name: html
mountPath: /usr/share/nginx/html
initContainers:
- name: index
image: bash
command:
- 'bash'
- '-c'
- 'echo "${APP^^}
" > /data/index.html'
env:
- name: APP
valueFrom:
fieldRef:
fieldPath: metadata.labels['app']
volumeMounts:
- name: html
mountPath: /data
volumes:
- name: html
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: product
labels:
app: product
spec:
selector:
app: product
ports:
- port: 80
EOF
```
7. 리소스가 정상적으로 생성되었는지 확인
```
kubectl get all -l app=product
```
8. */product* 경로로 접속할 경우 위에 배포한 서비스로 연결되도록 Ingress 생성
```
cat <${APP^^}" > /data/$APP/index.html'
env:
- name: APP
valueFrom:
fieldRef:
fieldPath: metadata.labels['app']
volumeMounts:
- name: html
mountPath: /data
volumes:
- name: html
emptyDir: {}
EOF
```
20. Product 서비스의 루트 경로 호출
```
kubectl exec deploy/product -- curl -s localhost
```
21. Product 서비스의 */product* 경로 호출
```
kubectl exec deploy/product -- curl -sL localhost/product
```
22. 처음에 생성한 Ingress의 ALB 엔드포인트에 */product* 경로로 웹브라우저를 통해서 접근이 되는지 확인 - *아래의 명령어로 주소 확인 가능*
```
echo $(kubectl get ing my-service -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}')/product
```
23. Payment 서비스 배포
```
cat <<'EOF' | kubectl apply -f -
apiVersion: apps/v1
kind: Deployment
metadata:
name: payment
labels:
app: payment
spec:
selector:
matchLabels:
app: payment
template:
metadata:
labels:
app: payment
spec:
containers:
- name: payment
image: nginx
ports:
- containerPort: 80
volumeMounts:
- name: html
mountPath: /usr/share/nginx/html
initContainers:
- name: index
image: bash
command:
- 'bash'
- '-c'
- 'mkdir /data/$APP && echo "${APP^^}
" > /data/$APP/index.html'
env:
- name: APP
valueFrom:
fieldRef:
fieldPath: metadata.labels['app']
volumeMounts:
- name: html
mountPath: /data
volumes:
- name: html
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: payment
labels:
app: payment
spec:
selector:
app: payment
ports:
- port: 80
EOF
```
24. 리소스가 정상적으로 생성되었는지 확인
```
kubectl get all -l app=payment
```
25. */payment* 경로로 접속할 경우 위에 배포한 서비스로 연결되도록 Ingress 생성
```
cat <
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.