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
[release-4.7] Bug 1954097: Annotate services of type LoadBalancer with user tags (AWS only) #606
[release-4.7] Bug 1954097: Annotate services of type LoadBalancer with user tags (AWS only) #606
Conversation
If the infrastructure object (on AWS) has additional user supplied resource tags specified then annotate services of type LoadBalancer as follows: "service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags": "Key1=Value1,KeyN=ValueN" https://issues.redhat.com/browse/NE-563 This is only done at create time, per the enhancement proposal. Existing services are not tagged. Equally, no reconciliation is done if the resource keys/values change.
/bugzilla refresh |
@frobware: This pull request references Bugzilla bug 1954097, which is invalid:
Comment In 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. |
@frobware: This pull request references Bugzilla bug 1954097, which is invalid:
Comment In 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. |
/hold This is waiting on 4.7 backports of: |
@frobware: This pull request references Bugzilla bug 1954097, which is invalid:
Comment In 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. |
4.7 openshift/api backport - openshift/api#914 |
/bugzilla refresh |
@frobware: An error was encountered querying GitHub for users with public email (hongli@redhat.com) for bug 1954097 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: i/o timeout
Please contact an administrator to resolve this issue, then request a bug refresh with In 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. |
/refresh |
@frobware: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@frobware: This pull request references Bugzilla bug 1954097, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
@frobware: This pull request references Bugzilla bug 1954097, which is invalid:
Comment In 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. |
/bugzilla refresh |
@frobware: This pull request references Bugzilla bug 1954097, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
/hold cancel openshift/api#914 has merged and we only need that for this to build and pass CI. |
@frobware: This pull request references Bugzilla bug 1954097, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
Not sure if this is a flake ATM: INFO[2021-04-29T10:21:35Z] operator_test.go:1883: deleted ingresscontroller headercapture /test e2e-aws-operator |
[sig-api-machinery][Feature:APIServer][Late] kube-apiserver terminates within graceful termination period [Suite:openshift/conformance/parallel] -- failed /retest |
Hmm. /retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: frobware, sgreene570 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ClusterVersion: Installing "" for : /retest |
@frobware: All pull requests linked via external trackers have merged: Bugzilla bug 1954097 has been moved to the MODIFIED state. In 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. |
This is a manual backport of #578.
This needs the following 4.7 backports:
And this PR to stand up a cluster and test e2e: