Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CD pipeline EKS #13

Closed
junha-ahn opened this issue Jul 14, 2023 · 2 comments
Closed

CD pipeline EKS #13

junha-ahn opened this issue Jul 14, 2023 · 2 comments

Comments

@junha-ahn
Copy link
Owner

junha-ahn commented Jul 14, 2023

image

학습 키워드

  • kubernetes
  • helm
  • EKS
  • argoCD
@junha-ahn
Copy link
Owner Author

junha-ahn commented Jul 14, 2023

image

자동화된 CICD pipe라인을 갖지만, 분리된 CD pipeline을 갖게 된다.

image

  • real time update of applications state

image

How to setting ArgoCD in k8s

image

@junha-ahn
Copy link
Owner Author

9 Ways to Expose an App on Amazon EKS to the Internet

kubeproxy only works on the application level

Load-balancer

  • aws-load-balancer-internal: false => private (only access in the vpc)
resoure "aws_route53_record" "web" {
    type = "CNAME"
    records = "k8s-5example-nginx....elb.us-east-2.amazonaws.com"
}

aws_load_balancer_controller

  • AWS Load Balancer Controller (이전 이름 : ALB Ingress Controller)

Ingress

  • Ingress를 사용해도 LoadBalancer를 사용한다.

image

  1. Ingress Controller(nginx ingresscontroller)를 EKS cluster에 배포한다 (다른 Application처럼)
  2. Ingress Controller가 AWS Load Balancer를 생성한다
  3. ALB => Ingress Controller => Service (base on the rules)
  4. 모니터링 툴이 Ingress Controller를 감시한다.

image

  • Native AWS Ingress Controller ALB VS Nginx Ingress Controller + NLB
  • 하나의 ALB로 모든 Service에 targeting 이 가능하다.
  • ALB는 NLB보다 비싸고 느리다

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant