You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.:
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.
The text was updated successfully, but these errors were encountered:
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.: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.
The text was updated successfully, but these errors were encountered: