Skip to content
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

Allow name of cluster-autoscaler status ConfigMap to be specificed #3888

Merged
merged 3 commits into from
Mar 11, 2021

Conversation

mrak
Copy link
Contributor

@mrak mrak commented Feb 17, 2021

Adds --status-config-map-name, which defaults to the original value of cluster-autoscaler-status.

This allows us to run two instances of cluster-autoscaler in our cluster, targeting two different types of autoscaling groups that require different command-line settings to be passed.

Do you foresee this causing any issues with the cluster-wide portion of the configmap status?

This allows us to run two instances of cluster-autoscaler in our
cluster, targeting two different types of autoscaling groups that
require different command-line settings to be passed.
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 17, 2021
@k8s-ci-robot
Copy link
Contributor

Welcome @mrak!

It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 17, 2021
@mrak
Copy link
Contributor Author

mrak commented Feb 18, 2021

/assign @feiskyer

Copy link
Contributor

@elmiko elmiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems reasonable to me, i think it would be worthwhile to update the parameter list in the faq as well.

Do you foresee this causing any issues with the cluster-wide portion of the configmap status?

looking around the code, i don't think this change will negatively impact the configmap status. but i'm not sure i get what you mean by "cluster-wide portion". iiuc each autoscaler will write its own status to the configmap, which sounds like what you want for your topology.

@mrak
Copy link
Contributor Author

mrak commented Mar 3, 2021

I'll see about updating the FAQ.

I meant the Cluster-wide portion like it appears here in the status ConfigMap:

Cluster-autoscaler status at 2021-03-03 15:38:29.243693431 +0000 UTC:
Cluster-wide:
  Health:      Healthy (ready=12 unready=0 notStarted=0 longNotStarted=0 registered=12 longUnregistered=0)
               LastProbeTime:      2021-03-03 15:38:29.240488873 +0000 UTC m=+52443.391263853
               LastTransitionTime: 2021-03-03 01:05:02.436510487 +0000 UTC m=+36.587285469
  ScaleUp:     NoActivity (ready=12 registered=12)
               LastProbeTime:      2021-03-03 15:38:29.240488873 +0000 UTC m=+52443.391263853
               LastTransitionTime: 2021-03-03 01:05:02.436510487 +0000 UTC m=+36.587285469
  ScaleDown:   NoCandidates (candidates=0)
               LastProbeTime:      2021-03-03 15:38:29.240488873 +0000 UTC m=+52443.391263853
               LastTransitionTime: 2021-03-03 01:36:27.848962781 +0000 UTC m=+1921.999737689

NodeGroups:
  Name:        asg-name-us-east-2a
  Health:      Healthy (ready=2 unready=0 notStarted=0 longNotStarted=0 registered=2 longUnregistered=0 cloudProviderTarget=2 (minSize=2, maxSize=5))
               LastProbeTime:      2021-03-03 15:38:29.240488873 +0000 UTC m=+52443.391263853
               LastTransitionTime: 2021-03-03 01:05:02.436510487 +0000 UTC m=+36.587285469
  ScaleUp:     NoActivity (ready=2 cloudProviderTarget=2)
               LastProbeTime:      2021-03-03 15:38:29.240488873 +0000 UTC m=+52443.391263853
               LastTransitionTime: 2021-03-03 01:05:02.436510487 +0000 UTC m=+36.587285469
  ScaleDown:   NoCandidates (candidates=0)
               LastProbeTime:      2021-03-03 15:38:29.240488873 +0000 UTC m=+52443.391263853
               LastTransitionTime: 2021-03-03 01:16:23.041505368 +0000 UTC m=+717.192280277

Copy link
Contributor

@elmiko elmiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems reasonable to me
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 4, 2021
@mrak
Copy link
Contributor Author

mrak commented Mar 10, 2021

/assign @feiskyer

Copy link
Contributor

@mwielgus mwielgus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elmiko, mrak, mwielgus

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 11, 2021
@k8s-ci-robot k8s-ci-robot merged commit 43ab030 into kubernetes:master Mar 11, 2021
joaovitor added a commit to joaovitor/autoscaler that referenced this pull request Mar 18, 2021
aksentyev pushed a commit to aksentyev/autoscaler that referenced this pull request Apr 9, 2021
piotrnosek pushed a commit to piotrnosek/autoscaler that referenced this pull request Nov 30, 2021
himanshu-kun pushed a commit to himanshu-kun/autoscaler that referenced this pull request Apr 11, 2022
galina-tochilkin pushed a commit to mtp-devops/3d-party-helm that referenced this pull request Aug 17, 2022
tim-smart pushed a commit to arisechurch/autoscaler that referenced this pull request Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants