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

Leverage deprecated features subsystem and feature flags #1778

Open
Zerpet opened this issue Nov 22, 2024 · 1 comment
Open

Leverage deprecated features subsystem and feature flags #1778

Zerpet opened this issue Nov 22, 2024 · 1 comment
Labels
never-stale Issue or PR marked to never go stale

Comments

@Zerpet
Copy link
Collaborator

Zerpet commented Nov 22, 2024

Is your feature request related to a problem?

RabbitMQ upgrades require certain number of feature flags to be enabled. Specially in the upgrade from 3.13.x to 4.0.x, we require all stable feature flags enabled, and khepri 3.13 disabled. This information is visible in the management UI, but it's not exposed in the CR status.

Describe the solution you'd like

Expose in the CR status if a deprecated feature is used, or if not all stable feature flags are enabled.

Describe alternatives you've considered

Automatically enable all feature flags after a rolling update, or as post-deploy steps.

This comment has been minimized.

@github-actions github-actions bot added the stale Issue or PR with long period of inactivity label Jan 22, 2025
@Zerpet Zerpet added never-stale Issue or PR marked to never go stale and removed stale Issue or PR with long period of inactivity labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
never-stale Issue or PR marked to never go stale
Projects
None yet
Development

No branches or pull requests

1 participant