BUG 1702050: Add aws role labels back (revert #1474)#1686
BUG 1702050: Add aws role labels back (revert #1474)#1686openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
We dropped aws role labels in openshift#1474 to reducethe surface to what's actually needed by our core controllers. However having this lables provides better UX and searchability for end users and consumers like machineAutoscaler resource so we are putting them back
|
/lgtm |
|
/retest |
|
/approve |
|
Are there docs for |
|
@wking we don't have that documented yet, we'll have something soon |
|
@wking FYI created openshift/machine-api-operator#306 |
|
Are these labels actually specific to the cloud? They seem fairly agnostic. Is there a standard convention, similar to node labels like OS/Role/Failure-Domain? |
|
/test e2e-aws-upgrade |
|
@chancez is up to the consumer to set this labels today. We might consider some standard for pre populating from the controller side in the future |
|
@enxebre So in practice they're arbitrary right? So they're not at all AWS specific. Perhaps in that case you guys could just re-use the labels used for nodes to indicate the role? Would make it somewhat simpler to document and explain the labels. Otherwise I guess maybe adjusting the PR title/commit description to indicate these aren't actually AWS specific labels, but rather just arbitrary labels set by the installer when using the AWS cloud provider. |
|
/lgtm |
|
/assign @staebler |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre, frobware, sdodson, spangenberg, staebler 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 |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
We dropped aws role labels in #1474 to reduce the surface to what's actually needed by our core controllers. However having this lables provides better UX and searchability for end users and consumers like machineAutoscaler resource so we are putting them back