[Kubernetes] CLUE 프로젝트 도입

[yunsangr]

CLUE 프로젝트 Minikube로 배포

69번에서 실행되고 있는 mdwalks-clue 서비스를 minikube를 사용해 130번서버(윤상열 개인서버)로 배포해봅니다.

35 을 참고합니다.

[yunsangr]

2021년 10월 27일 수요일 작업로그

API/Nginx Docker-compose

• kompose 를 사용해 docker-compose 를 k8s 에서 실행해보자
• kompose: 기존에 docker-compose를 k8s 환경에서 사용가능하게 yaml 파일 만들어주는 소프트웨어
• kubernetes + docker-compose = kompose 제법 귀여운 네이밍

  > sudo snap install kompose # snap 을 사용해 kompose 설치
  kompose 1.21.0 from Ricardo Amendoeira (ric2b) installed
  > kompose convert -f docker-compose.yml --out docker-kompose.yml 
  FATA Version 3.8 of Docker Compose is not supported. Please use version 1, 2 or 3 # Docker Compose 1, 2 or 3 버젼만 지원되니 docker-compose.yml 에서 버젼을 3으로 변경
  > kompose convert -f docker-compose.yml --out docker-kompose.yml # docker-compose.yml -> docker-kompose.yml로 전환
  INFO Service name in docker-compose has been changed from "converter_worker" to "converter-worker" 
  INFO Service name in docker-compose has been changed from "extractor_worker" to "extractor-worker" 
  INFO Service name in docker-compose has been changed from "generator_worker" to "generator-worker" 
  INFO Service name in docker-compose has been changed from "batch_worker" to "batch-worker"
  > minikube image load mdwalks_clue_api_develop:126      # k8s 에 api 이미지 로드
  > minikube image load mdwalks_clue_nginx_develop:126  # k8s 에 nignx 이미지 로드
  > kubectl apply -f docker-kompose.yml                           
  service/api created
  service/nginx created
  service/redis created
  deployment.apps/api created
  persistentvolumeclaim/web created
  deployment.apps/batch-worker created
  deployment.apps/converter-worker created
  persistentvolumeclaim/web configured
  deployment.apps/extractor-worker created
  deployment.apps/generator-worker created
  deployment.apps/nginx created
  deployment.apps/redis created

  결과는 실패

• 서비스 설정이 아직 한번에 되지 않아 생긴걸로 추정?

  
  > minikube service list  
  |----------------------|---------------------------|--------------|---------------------------|
  |      NAMESPACE       |           NAME            | TARGET PORT  |            URL            |
  |----------------------|---------------------------|--------------|---------------------------|
  | default              | api                       | No node port |
  | default              | clue-cdn                  |         4000 | http://192.168.49.2:30976 |
  | default              | hello-node                |         8080 | http://192.168.49.2:32098 |
  | default              | kubernetes                | No node port |
  | default              | nginx                     | No node port |
  | default              | redis                     | No node port |
  | kube-system          | kube-dns                  | No node port |
  | kubernetes-dashboard | dashboard-metrics-scraper | No node port |
  | kubernetes-dashboard | kubernetes-dashboard      | No node port |
  |----------------------|---------------------------|--------------|---------------------------|

- converer-worker/nginx 컨테이너에서 `Back-off restarting failed container` 가 발생
- converter-worker:

FileNotFoundError: [Errno 2] No such file or directory: '/mdwalks_clue/files/log/converters.log'

- nginx

2021/10/27 07:44:13 [emerg] 1#1: host not found in upstream "mdwalks_clue_develop_api_1:8000" in /etc/nginx/conf.d/api_reverse_proxy.conf:5 nginx: [emerg] host not found in upstream "mdwalks_clue_develop_api_1:8000" in /etc/nginx/conf.d/api_reverse_proxy.conf:5

#### 참고 링크
https://kompose.io/

[yunsangr]

2021년 10월 29일 작업로그

• nginx 아직 host not found in upstream 해결 못함
  • minikube ssh 접속 후 api container 이름을 강제로 mdwalks_clue_develop_api_1 으로 rename 해보았지만 실패
• nginx 제거 후 api swagger 접속 성공
• docker-compose api service에 아래 값들 추가해야 외부에서 접근 가능

  api:
  image: "mdwalks_clue_api_develop:126"
  entrypoint: bash bin/run_server.sh 8000
  expose:
    - 8000
  depends_on:
    - redis
  volumes:
    - web:/mdwalks_clue/files
  labels:
    kompose.service.type: nodeport

  service.type 추가로 결과 화면

  
  (base) ➜  kubernetes minikube service list              
  |----------------------|---------------------------|--------------|---------------------------|
  |      NAMESPACE       |           NAME            | TARGET PORT  |            URL            |
  |----------------------|---------------------------|--------------|---------------------------|
  | default              | api                       | 8000/8000    | http://192.168.49.2:32510 |
  | default              | clue-cdn                  |         4000 | http://192.168.49.2:30976 |
  | default              | hello-node                |         8080 | http://192.168.49.2:32098 |
  | default              | kubernetes                | No node port |
  | default              | nginx                     | 8888/8888    | http://192.168.49.2:31293 |
  | default              | redis                     | No node port |
  | kube-system          | kube-dns                  | No node port |
  | kubernetes-dashboard | dashboard-metrics-scraper | No node port |
  | kubernetes-dashboard | kubernetes-dashboard      | No node port |
  |----------------------|---------------------------|--------------|---------------------------|

[yunsangr]

2021년 11월 5일 작업로그

목표: nginx ingress controller 정상 구동

• Ingress는 Pod, ReplicaSet, Deployment, Service와 달리 addons 에서 활성화 해야한다.

  
  > minikube addons enable ingress
  ▪ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
  ▪ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
  ▪ Using image k8s.gcr.io/ingress-nginx/controller:v1.0.0-beta.3
  🔎  Verifying ingress addon...
  🌟  The 'ingress' addon is enabled

ingress 컨트롤러 확인

minikube addons list	-----------------------------	----------	--------------	-----------------------		ADDON NAME	PROFILE	STATUS	MAINTAINER
ambassador	minikube	disabled	unknown (third-party)
auto-pause	minikube	disabled	google
csi-hostpath-driver	minikube	disabled	kubernetes
dashboard	minikube	enabled ✅	kubernetes
default-storageclass	minikube	enabled ✅	kubernetes
efk	minikube	disabled	unknown (third-party)
freshpod	minikube	disabled	google
gcp-auth	minikube	disabled	google
gvisor	minikube	disabled	google
helm-tiller	minikube	disabled	unknown (third-party)
ingress	minikube	enabled ✅	unknown (third-party)
ingress-dns	minikube	disabled	unknown (third-party)
istio	minikube	disabled	unknown (third-party)
istio-provisioner	minikube	disabled	unknown (third-party)
kubevirt	minikube	disabled	unknown (third-party)
logviewer	minikube	disabled	google
metallb	minikube	disabled	unknown (third-party)
metrics-server	minikube	disabled	kubernetes
nvidia-driver-installer	minikube	disabled	google
nvidia-gpu-device-plugin	minikube	disabled	unknown (third-party)
olm	minikube	disabled	unknown (third-party)
pod-security-policy	minikube	disabled	unknown (third-party)
portainer	minikube	disabled	portainer.io
registry	minikube	disabled	google
registry-aliases	minikube	disabled	unknown (third-party)
registry-creds	minikube	disabled	unknown (third-party)
storage-provisioner	minikube	enabled ✅	kubernetes
storage-provisioner-gluster	minikube	disabled	unknown (third-party)
volumesnapshots	minikube	disabled	kubernetes
-----------------------------	----------	--------------	-----------------------

- 활성화된 ingress를 확인합니다.
```sh
> minikube ip                               
192.168.49.2
> curl -I http://192.168.49.2/healthz
HTTP/1.1 200 OK
Date: Fri, 05 Nov 2021 01:08:15 GMT
Content-Type: text/html
Content-Length: 0
Connection: keep-alive

참고링크

k8s ingress 안내서