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

Bump rukpak to v0.14.0 #446

Closed
joelanford opened this issue Oct 9, 2023 · 0 comments · Fixed by #448
Closed

Bump rukpak to v0.14.0 #446

joelanford opened this issue Oct 9, 2023 · 0 comments · Fixed by #448
Assignees
Milestone

Comments

@joelanford
Copy link
Member

Rukpak v0.14.0 adds a new Healthy condition to BundleDeployments. It would be great to pull this version of Rukpak into Operator Controller so that users have more visibility into the state of their cluster.

Follow-ups that we should capture for after bumping the version:

  1. Sync the BD healthy condition into Operator status, so that clients interacting solely with the Operator API have information about the health of the operator.
  2. Consider BD health when determining whether an upgrade should proceed. If the BD for an Operator is not healthy, don't upgrade.
  3. Add a knob in the Operator API that allows a cluster admin to proceed with an upgrade even if the BD is unhealthy.

See #434 for dependabot's rukpak version bump attempt. It looks like we have some tests that are overly particular about the BD conditions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants