Set constraint to progressing to prevent it from being displayed as error in the dashboard.#12470
Conversation
gardener-prow
bot
added
cla: yes
|
@axel7born: GitHub didn't allow me to request PR reviews from the following users: grolu. Note that only gardener members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
ScheererJ
left a comment
ScheererJ
left a comment
There was a problem hiding this comment.
/assign
Thanks for improving the usability of the dual-stack migration.
/lgtm
/approve
|
LGTM label has been added. DetailsGit tree hash: 3bee3a57afa020f4eaee89c9033a0f4a7378b67e |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ScheererJ The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
gardener-prow
bot
added
the
approved
being displayed as error in the dashboard.
axel7born
force-pushed
the
enh/node-constraint-progessing
branch
from
9d5c1c0 to
5ab8090
Compare
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: a398e5a24570fbedd5a0102c11f1cec4c149fb66 |
3 participants
How to categorize this PR?
/area networking
/kind enhancement
What this PR does / why we need it:
The constraint
DualStackNodesMigrationReadyis used to track, if the nodes in the shoot are prepared for a migration of the shoot to dual-stack networking. However, a constraint with statusfalseis displayed as error in the gardener dashboard. As this is confusing users, we change the constraint status toprogressingwhich will be displayed in the dashboard with gardener/dashboard#2503.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: