TODO: Bring K8s Ingress in Helm chart

[jihoon-seo]

[Usage]

• Ingress -> cb-webtool
• Ingress -> cb-restapigw (Or, make Ingress work as REST API GW)
• Ingress -> cb-grpcproxy (Or, make Ingress work as gRPC Proxy)

[Options]

• Nginx
• Kong
• Traefik
• Istio + Envoy

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.86. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[jihoon-seo]

[References]

• [쿠버네티스 Ingress 개념 및 사용 방법, 온-프레미스 환경에서 Ingress 구축하기] (https://blog.naver.com/alice_k106/221502890249)
• [(타다) AWS 서비스를 활용한 Kubernetes 클러스터 구축] (http://engineering.vcnc.co.kr/2019/03/kubernetes-on-aws/)
• [쿠버네티스 #8 - Ingress] (https://bcho.tistory.com/1263)
• [Kubernetes NodePort vs LoadBalancer vs Ingress?? 언제 무엇을 써야 할까??] (https://blog.leocat.kr/notes/2019/08/22/translation-kubernetes-nodeport-vs-loadbalancer-vs-ingress)
• Google "k8s ingress"

[jihoon-seo]

[K8s Ingress rules]

• An optional host.
  • 예
  • cb-spider-grpc.mycompany.com (Ingress controller) → cb-spider.[namespace].svc.cluster.local (Actual CB-Spider svc))
• A list of paths (for example, /testpath). (SEO 주: Path 로 구분하는 것은 REST 에 대해서는 가능하나 gRPC 에 대해서는 불가능..?)

---

[gRPC 서비스 구분은 URI path 보다는 :authority 헤더나 :path 헤더를 이용하라는 글]

• https://github.com/grpc/grpc/issues/14900

[gRPC URI에 prefix 넣는 것은 strongly discouraged 된다는 글]

• https://github.com/grpc/grpc-dotnet/issues/110

[K8s VirtualService 이용하여 URL prefix를 rewrite (여기서는 strip) 하라는 글]

• https://stackoverflow.com/questions/62459006/how-to-route-multiple-grpc-services-based-on-path-in-istiokubernetes

---

[K8s Ingress - gRPC routing rules 예제]

• RPC 헤더를 이용하여 route https://www.alibabacloud.com/blog/accessing-grpc-services-through-container-service-for-kubernetes-ingress-controller_594315