Improve cluster deployment status for nested infra (#1044) #1121
+48
−11
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.
kubectl get clusterdeployment
output #1027It was inconvenient that we couldn't see the status of AwsCluster (VPC threshold, Credential invalid, etc.). An issue has already been filed. So I have tried to add the cluster information of Cluster's InfraRef to ClusterDeployment's Conditions.
If you already have other designs or ideas, I want to try to rework that also close this one.
This is sample flow on my testing.
Add message example:
my-aws-clusterdeployment1: failed to create new managed VPC: failed to create vpc: AuthFailure: AWS was not able to validate the provided access credentials...