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

[enhancement] Add status condition to Management object to make it kstate-compatible #807

Open
Algeran opened this issue Dec 18, 2024 · 0 comments
Labels
enhancement Small feature, request or improvement suggestion

Comments

@Algeran
Copy link

Algeran commented Dec 18, 2024

Is your enhancement / feature request related to a problem? Please describe.
When I deploy the P2A operator itself, it starts to deploy multiple components under the hood and the only option I found to check if everything is up and running is to monitor the Management object with various scripts and bash commands. E.g.:

kubectl get management hmc -o json | jq -r '.status.components | to_entries[] | "\(.key): \(.value.success // .value.error)"'

But this object type doesn’t actually have any status field that can indicate that the platform is ready. In the base output it has only name and age, but nothing about the components state.

Describe the solution you'd like
It would be great to expose the status of the Management object with the information about the platform readiness and especially adding the usual kubernetes status condition to make the objects kstate-compatible.
It will help to automate deployments of the platform lot. For example, it can be used in flux as healtcheck.

@Algeran Algeran added the enhancement Small feature, request or improvement suggestion label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Small feature, request or improvement suggestion
Projects
Status: Todo
Development

No branches or pull requests

1 participant