📗 프로비저닝 - Nginx Ingress Controller

🏳️‍🌈 [궁금한점]

• Bitnami 차트를 이용한 Nginx 설치 방법

문서 연결

• (선행) Nginx 가 서비스로 설치 및 실행되어야 함- Provisioning - Nginx

---

🔗[목차]

• Nginx Ingress Controller 설치
  • 1️⃣ 준비
    • Nginx Web Server 설치 ( Ingress 동작 확인 용)
    • 헬름 차트 다운로드
    • 사용자 도메인 설정
  • 2️⃣ 설정 - 사용자 Values 파일 생성
  • 3️⃣ 설치 - Nginx Ingress Controller 설치
  • 4️⃣ Ingress 생성
  • 5️⃣ 검증 - 라우팅
    • Path 기반 라우팅
• 디버깅
  • 로그 보기
  • 컨트롤러, 서비스 간 연결 확인
  • CURL 테스트
  • Ingress Controller 재시작
  • External Traffic 정책 변경 (Bitnami 는 기본값이 Cluter)

Nginx Ingress Controller 설치

1️⃣ 준비

Nginx Web Server 설치 ( Ingress 동작 확인 용)

Provisioning - Nginx

헬름 차트 다운로드

helm pull oci://registry-1.docker.io/bitnamicharts/nginx-ingress-controller --untar

Pulled: registry-1.docker.io/bitnamicharts/nginx-ingress-controller:11.6.21
Digest: sha256:56867b254ee8150c39b4444d455e909fec1508b2f3d45ba856496d1e492be371

cd nginx-ingress-controller

사용자 도메인 설정

• C:\Windows\System32\drivers\etc\hosts 파일 편집
• 192.168.56.10 은 K8s master node IP
• example.local 는 사용자 지정 도메인 명

192.168.56.10 example.local

Ping test

ping example.local

Ping example.local [192.168.56.10] 32바이트 데이터 사용:
192.168.56.10의 응답: 바이트=32 시간<1ms TTL=64
192.168.56.10의 응답: 바이트=32 시간<1ms TTL=64

## 2️⃣ 설정 - 사용자 Values 파일 생성
``` bash
cp values.yaml dev-values.yaml

• dev-values.yaml 파일 편집
• 아래 내용 남기고 삭제

service:
  type: NodePort

3️⃣ 설치 - Nginx Ingress Controller 설치

helm install nginx-ingress . -n nginx-ingress --create-namespace -f dev-values.yaml

helm install nginx-ingress . -n nginx-ingress --create-namespace -f dev-values.yaml
NAME: nginx-ingress
LAST DEPLOYED: Fri May 30 15:59:47 2025
NAMESPACE: nginx-ingress
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
CHART NAME: nginx-ingress-controller
CHART VERSION: 11.6.21
APP VERSION: 1.12.2

Did you know there are enterprise versions of the Bitnami catalog? For enhanced secure software supply chain features, unlimited pulls from Docker, LTS support, or application customization, see Bitnami Premium or Tanzu Application Catalog. See https://www.arrow.com/globalecs/na/vendors/bitnami for more information.

** Please be patient while the chart is being deployed **

The nginx-ingress controller has been installed.

Get the application URL by running these commands:
    export HTTP_NODE_PORT=$(kubectl --namespace nginx-ingress get services -o jsonpath="{.spec.ports[0].nodePort}" nginx-ingress-nginx-ingress-controller)
    export HTTPS_NODE_PORT=$(kubectl --namespace nginx-ingress get services -o jsonpath="{.spec.ports[1].nodePort}" nginx-ingress-nginx-ingress-controller)
    export NODE_IP=$(kubectl --namespace nginx-ingress get nodes -o jsonpath="{.items[0].status.addresses[1].address}")

    echo "Visit http://$NODE_IP:$HTTP_NODE_PORT to access your application via HTTP."
    echo "Visit https://$NODE_IP:$HTTPS_NODE_PORT to access your application via HTTPS."

An example Ingress that makes use of the controller:

  apiVersion: networking.k8s.io/v1
  kind: Ingress
  metadata:
    name: example
    namespace: nginx-ingress
  spec:
    ingressClassName: nginx
    rules:
      - host: www.example.com
        http:
          paths:
            - backend:
                service:
                  name: example-service
                  port:
                    number: 80
              path: /
              pathType: Prefix
    # This section is only required if TLS is to be enabled for the Ingress
    tls:
        - hosts:
            - www.example.com
          secretName: example-tls

If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:

  apiVersion: v1
  kind: Secret
  metadata:
    name: example-tls
    namespace: nginx-ingress
  data:
    tls.crt: <base64 encoded cert>
    tls.key: <base64 encoded key>
  type: kubernetes.io/tls

WARNING: There are "resources" sections in the chart not set. Using "resourcesPreset" is not recommended for production. For production installations, please set the following values according to your workload needs:
  - defaultBackend.resources
  - resources
+info https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

리소스 확인

k get all -n nginx-ingress

NAME READY STATUS RESTARTS AGE
pod/nginx-ingress-nginx-ingress-controller-85794f8d67-k8tns 1/1 Running 0 2m12s
pod/nginx-ingress-nginx-ingress-controller-default-backend-76fltg4k 1/1 Running 0 2m12s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/nginx-ingress-nginx-ingress-controller NodePort 10.102.94.244 80:31158/TCP,443:30291/TCP 2m12s
service/nginx-ingress-nginx-ingress-controller-default-backend ClusterIP 10.102.220.112 80/TCP 2m12s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/nginx-ingress-nginx-ingress-controller 1/1 1 1 2m12s
deployment.apps/nginx-ingress-nginx-ingress-controller-default-backend 1/1 1 1 2m12s

NAME DESIRED CURRENT READY AGE
replicaset.apps/nginx-ingress-nginx-ingress-controller-85794f8d67 1 1 1 2m12s
replicaset.apps/nginx-ingress-nginx-ingress-controller-default-backend-76f6b46974 1 1 1 2m12s

## 4️⃣ Ingress 생성
- 서비스 명은 현재 기동중인 nginx 의 서비스명 
- [Nginx 설치 참고](provisioning-nginx.md)
- 파일명 myingress.yaml
- `k apply -f myingress.yaml` 로 적용
``` yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/use-regex: "true"
spec:
    kubernetes.io/ingress.class: "nginx"
  namespace: mydev
spec:
  ingressClassName: nginx
  rules:
  - host: example.local
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: mynginx
            port:
              number: 80
      - path: /sky(/|$)(.*)
        pathType: Prefix
        backend:
          service:
            name: mynginx
            port:
              number: 80  
            

Ingress 적용 확인

k get ing -n mydev

NAME CLASS HOSTS ADDRESS PORTS AGE
myingress nginx example.local 80 62s

> ### Nginx Ingress Controller 로그 확인
- myingress가 추가되었다는 로그 확인
``` bash
k get po -n nginx-ingress
NAME                                        READY   STATUS    RESTARTS   AGE
nginx-ingress-controller-6d9bd896cf-5g972   1/1     Running   0          25m

k logs --tail=100 -f nginx-ingress-controller-6d9bd896cf-5g972 -n nginx-ingress

I20250528 12:05:00.018569   1 main.go:107] Event(v1.ObjectReferenceI20250530 04:14:19.510787   1 main.go:107] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"mydev", Name:"myingress", UID:"b83408fe-36f3-4301-b03f-68fb18b504f5", APIVersion:"networking.k8s.io/v1", ResourceVersion:"440697", FieldPath:""}): type: 'Normal' reason: 'AddedOrUpdated' Configuration for mydev/myingress was added or updated

5️⃣ 검증 - 라우팅

Nginx Ingress Controller 서비스 노드 포트 확인

k get svc -n nginx-ingress

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
nginx-ingress-controller NodePort 10.96.15.136 80:31346/TCP,443:31113/TCP 57m

### Path 기반 라우팅
``` bash
curl -k -H "Host: example.local" http://192.168.56.10:31158/
curl -k -H "Host: example.local" http://192.168.56.10:31158/sky
curl -k http://example.local:31158/

디버깅

로그 보기

kubectl logs --tail=100 -f <pod-name> -n <namespace>

컨트롤러, 서비스 간 연결 확인

kubectl exec -n nginx-ingress -it nginx-ingress-nginx-ingress-controller-85794f8d67-k8tns -- curl -s http://mynginx.mydev.svc.cluster.local:80/

CURL 테스트

vagrant@master:~$ curl -v -k -H "Host: example.local" http://192.168.56.10:31158/
*   Trying 192.168.56.10:31158...
* Connected to 192.168.56.10 (192.168.56.10) port 31158
> GET / HTTP/1.1
> Host: example.local
> User-Agent: curl/8.5.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Fri, 30 May 2025 07:06:50 GMT
< Content-Type: text/html
< Content-Length: 615
< Connection: keep-alive
< Last-Modified: Thu, 24 Apr 2025 14:31:11 GMT
< ETag: "680a4b2f-267"
< X-Frame-Options: SAMEORIGIN
< Accept-Ranges: bytes
<
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>
* Connection #0 to host 192.168.56.10 left intact

Ingress Controller 재시작

kubectl rollout restart deployment nginx-ingress-controller -n nginx-ingress
deployment.apps/nginx-ingress-controller restarted

External Traffic 정책 변경 (Bitnami 는 기본값이 Cluter)

kubectl patch svc nginx-ingress-controller -n nginx-ingress \
  -p '{"spec": {"externalTrafficPolicy": "Cluster"}}'

service/nginx-ingress-controller patched