-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Support custom tags for cloud provider managed resources #96450
Conversation
staging/src/k8s.io/legacy-cloud-providers/azure/azure_loadbalancer.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/legacy-cloud-providers/azure/azure_loadbalancer.go
Outdated
Show resolved
Hide resolved
/milestone v1.20 |
1106aa8
to
2e60a3d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/retest
/retest |
/hold |
8166664
to
824528c
Compare
/hold cancel |
/retest |
/lgtm |
/retest |
824528c
to
b337157
Compare
/lgtm |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feiskyer, nilo19 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Support custom tags for cloud provider managed resources, including shared resources (LB, security group, and route table) and non-shared resources (public IP). For shared resources, introducing a new cloud config
tags: "a=b,c=d,..."
. For public IP, introducing a new service annotationservice.beta.kubernetes.io/azure-pip-tags: "a=b,c=d,..."
. The corresponding resources would be tagged as configured when creating the cluster or after restarting the controller manager.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig cloud-provider
/area provider/azure
/priority important-soon
/triage accepted