-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Make cluster proportional autoscaler image configurable. #10564
Conversation
Welcome @bjhaid! |
Hi @bjhaid. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
@@ -1867,6 +1867,10 @@ spec: | |||
description: CoreDNSImage is used to override the default image | |||
used for CoreDNS | |||
type: string | |||
cpaImage: |
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.
I'm not sure this image override field should live under the kubeDNS
spec
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.
the image is only used by coredns and kubedns... which is why I kept it there.
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.
I am open to putting it elsewhere... under which object would you suggest I put it?
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.
Yeah I guess I was thinking since its more a general purpose autoscaler than just DNS but if its only used for DNS out of the box in a new cluster then seems fine for it be here!
Similar to how we can configure coreDNS image we will like to configure cluster Proportional autoscaler so we can use our internal docker registry rather than gcr.io.
/ok-to-test |
@olemarkus @joshbranham does this change look good enough to be approved? is either of you an approver? if not can you please help tag someone who can approve, thanks! |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bjhaid, olemarkus 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 |
@olemarkus thanks for approving! what do I need to do to get this backported? |
You need to create a backport issue and then we'll consider if it makes sense. See here https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md |
Similar to how we can configure coreDNS image we will like to configure
cluster Proportional autoscaler so we can use our internal docker
registry rather than gcr.io.