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

Deployment 환경에 따라 필요한 ingress annotation 차이에 대한 대응 #129

Open
JunhoeKim opened this issue Nov 9, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@JunhoeKim
Copy link
Collaborator

MPP 서비스를 하면서 발생한 502 이슈를 해결하기 위해서 아래와 같은 annotation을 도입하게 되었다.

  • nginx.ingress.kubernetes.io/client-body-buffer-size: 64m
  • nginx.ingress.kubernetes.io/proxy-body-size: 64m
  • nginx.ingress.kubernetes.io/proxy-buffer-size: 500k
  • nginx.ingress.kubernetes.io/proxy-connect-timeout: '600'
  • nginx.ingress.kubernetes.io/proxy-next-upstream-timeout: '600'
  • nginx.ingress.kubernetes.io/proxy-read-timeout: '600'
  • nginx.ingress.kubernetes.io/proxy-send-timeout: '600'

이런식으로 서비스의 부하 정도에 따라 필요한 annotation이 달라져서 이에 대한 처리를 어떻게 해야할지 고민이 필요하다.

@JunhoeKim JunhoeKim added the enhancement New feature or request label Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant