CFE-688: Update install-config CRD to support gcp labels and tags#7126
CFE-688: Update install-config CRD to support gcp labels and tags#7126patrickdillon merged 1 commit intoopenshift:masterfrom
Conversation
|
@bharath-b-rh: This pull request references CFE-688 which is a valid jira issue. 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/test-infra repository. |
7f65334 to
f623593
Compare
f734be4 to
1d73d45
Compare
|
/label qe-approved |
|
/remove-hold |
|
/retest-required |
1 similar comment
|
/retest-required |
cf39b5f to
102927c
Compare
patrickdillon
left a comment
There was a problem hiding this comment.
The featuregate validation looks better but it is still not quite right (the default feature set is not populating the feature gates). But I think the feature gate validation is turning out to be a big lift and we should remove it from this PR, so that this PR can stay focused on the GCP labels and tags. I have started #7413 to handle the feature gate validation. That implementation stays pretty close to what is in the cluster-config-operator. Let's iterate on the feature gates in a separate PR and focus this one solely on the GCP labels and tags.
I think keeping just the TechPreviewNoUpgrade condition for the feature and a separate PR to handle other FeatureSets should be fine? |
|
@bharath-b-rh: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon 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 |
|
/skip |
|
/test e2e-gcp-ovn |
|
/retest |
PR is for adding new fields userLabels and userTags for gcp platform type, to add user defined labels and tags to all those gcp resources created by installer.