-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update Nexus CR Status to use the Conditions API #213
Comments
Some previous experience:
|
Yup. The idea is to have each condition in the array with the latest status and the status set to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Right now we are not keeping the entire history of the CR status in the Nexus object, what we have is:
Although is interesting to reflect the internal
Deployment
status, ideally we would carry the conditions array ourselves. See an example: https://medium.com/swlh/advanced-kubernetes-operators-development-988edad5f58a (Set Status Conditions section)Describe the solution you'd like
To add the
Status.Conditions[]
field to the Nexus CR.Describe alternatives you've considered
Right now we have only the latest "condition" described in our CR
Additional context
This article brings a glimpse about this implementation. But we can also see Knative CRs for other references.
The text was updated successfully, but these errors were encountered: