Repository navigation
Pin mc-web-console to v0.7.4 and raise the IAM nginx read timeout for the Web Console proxy - #242
Merged
Merged
Conversation
노드 삭제·전원 제어 등 mc-infra-manager 동기 API 는 CSP 작업이 끝난 뒤 응답한다(GCP 노드 삭제 약 62초). Web Console location 의 proxy_read_timeout 60s 보다 길어 작업은 성공하는데 브라우저는 504 를 받았다. - Web Console(:3001) location proxy_read_timeout 60s → 90s (prod/local 템플릿) - README/README_kr Known Issues 에 원인과 120s 상향 절차 기록
stage 실측에서 AWS EKS NodeGroup 생성이 99초 걸려 90초로도 504 가 났다. - Web Console(:3001) location proxy_read_timeout 90s → 120s (prod/local 템플릿) - README/README_kr Known Issues 실측값(노드 삭제 62초, NodeGroup 생성 99초)과 상향 절차 갱신
fix(iam-nginx): Web Console 프록시 응답 대기 시간을 120초로 늘림
chore: mc-web-console up to 0.7.4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's Changed
Version pin: mc-web-console v0.7.4
Apply the mc-web-console v0.7.4 release.
docker-compose.yaml,docker-compose.mini.yaml:cloudbaristaorg/mc-web-console-apiandmc-web-console-front0.7.3 → 0.7.4api.yaml(conf/,conf/docker/,conf/docker/conf/mc-web-console/api/conf/):mc-web-consoleversion 0.7.3 → 0.7.4IAM nginx: longer read timeout for the Web Console proxy
Some mc-infra-manager (CB-Tumblebug) APIs are synchronous and respond only after the CSP finishes (e.g.
DelInfraNode,GetControlInfraNode,PostK8sNodeGroup). The Web Console location in the IAM nginx usedproxy_read_timeout 60s, so the browser got 504 and a failure toast even though the operation completed successfully afterwards. Measured on a stage install: GCP node delete 62s, AWS EKS NodeGroup create 99s.conf/docker/conf/mc-iam-manager/nginx.template.conf,nginx.template.local.conf: Web Console (:3001) locationproxy_read_timeout60s → 120s. Connect/send timeouts and other service locations are unchangedREADME.md/README_kr.md(Known Issues): describe the cause, how to raise the value further if 504 still occurs (template, runningnginx.conf, reload), and how to confirm it fromdocker logs mc-iam-manager-nginxnginx.conf; apply the change there and reload nginx (steps in the README)