argocd: add custom health for cluster-api machinedeployment #18
Conversation
This file contains 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.
Cluster API MachineDeployment 자원은 CNI 배포를 통해 노드가 Ready 상태가 되어야만 AvailableReplicas 수를 업데이트해서 Health 상태로 전환됩니다. 하지만 ArgoCD가 모든 자원이 Health 상태가 아니라면 설치가 완료되지 않고 계속 기다리는 상황이 발생하고 이후 단계 (CNI 설치를 포함한)가 진행되지 않기 때문에 이를 우회하기 위한 커스텀 헬스 체크 부분 (spec과 status replicas 숫자를 비교)을 추가합니다.