Repository navigation
Profile rollout state - #204
Merged
gianlucam76 merged 1 commit intoOct 27, 2026
Merged
Conversation
Description A profile with maxUpdate does not reach all its matching clusters at once. The matching clusters table only showed the deployment status of each cluster's current ClusterSummary, so a cluster that is queued behind maxUpdate and still runs the previous configuration looked Provisioned. This shows where each matching cluster is in the rollout of the latest version of the profile. It uses the rolloutState and rollout fields that ui-backend now returns from GET /profile (ui-backend PR: <link>), so it needs that change before anything shows up. Matching clusters table: - A Rollout column next to Status, with a badge per cluster: Updated, Updating, Waiting, Paused or Not ready. Each badge has a tooltip saying what the state means, for example that a waiting cluster does not have the latest version yet and is queued because the maxUpdate limit is reached. - A filter above the table to list only the clusters in one state. It only offers states that have at least one cluster. It resets to All when the selected state has no cluster left. - Both appear only when at least one cluster has a rollout state. Profiles without a pending rollout or paused cluster look as before. Summary above the table, shown only while a rollout is pending: - "Rollout in progress", a progress bar and "3 of 10 clusters updated". - The count per state and "Max concurrent updates". When maxUpdate is a percentage, it is shown with the number of clusters it stands for, for example "30% (3)". - Paused clusters are not counted in the progress, the rollout skips them. Other changes: - The accordion that opens a cluster's feature list is now tracked by cluster identity instead of row position, so it stays correct when the filter changes the rows. - New strings in en.json, fr.json and ar.json. The French and Arabic are my translations and need a review by a native speaker. The Arabic follows the transliterations already used in the file (profile, cluster). The page does not poll, so a rollout in flight is shown as of the last load of the page.
gianlucam76
force-pushed
the
profile-rollout-state
branch
from
October 23, 2026 15:33
2794a88 to
d096806
Compare
Member
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.