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

[addon-resizer] deployment update drops existing toleration fields #188

Closed
djsly opened this issue Jul 25, 2017 · 14 comments
Closed

[addon-resizer] deployment update drops existing toleration fields #188

djsly opened this issue Jul 25, 2017 · 14 comments
Labels
area/addon-resizer lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@djsly
Copy link

djsly commented Jul 25, 2017

Probably due to the version of the k8s go client used by the addon-resizer

#kubectl create -f heapster-controller.yaml
deployment "heapster" created
# kubectl get deployment heapster -o yaml | grep tolerations -A6
      tolerations:
      - key: CriticalAddonsOnly
        operator: Exists
      - effect: NoSchedule
        key: role
        operator: Equal
        value: k8s-edge-node
# kubectl get deployment heapster -o yaml | grep tolerations -A6
      tolerations:
      - key: CriticalAddonsOnly
        operator: Exists
      - effect: NoSchedule
        key: role
        operator: Equal
        value: k8s-edge-node
# kubectl get deployment heapster -o yaml | grep tolerations -A6
# kubectl get deployment heapster -o yaml | grep tolerations -A6

Go client version

       {
            "ImportPath": "k8s.io/kubernetes/pkg/client/clientset_generated/release_1_3",
            "Comment": "v1.3.0-alpha.5-165-g7476d97",
            "Rev": "7476d97781563b70e8b89a8bd3f99ea75ae6c290"
        },
@djsly
Copy link
Author

djsly commented Jul 25, 2017

@piosz @wojtek-t @Q-Lee

@djsly
Copy link
Author

djsly commented Jul 25, 2017

@x13n @MaciekPytel since you guys seems to be the new owner :)

@djsly djsly changed the title [addon-resizer] deployment updates drops existing toleration fields [addon-resizer] deployment update drops existing toleration fields Jul 25, 2017
@x13n
Copy link
Member

x13n commented Jul 26, 2017

PodSpec used by pod_nanny (via DeploymentInterface -> Deployment -> DeploymentSpec -> PodTemplateSpec) doesn't have Tolarations field defined, looks like it's using an older definition of Pod. Old godeps?

@djsly
Copy link
Author

djsly commented Jul 26, 2017

looks like it indeed, from my understanding it is using an old k8s go client. version v1.3.0-alpha.5-165-g7476d97

@x13n
Copy link
Member

x13n commented Jul 26, 2017

@djsly I briefly chatted with @MaciekPytel today about this. Neither me nor him can look into this immediately, but this should get fixed some time between now and 1.8. This should be a matter of updating godeps. Of course, PR to fix this would be welcome.

@djsly
Copy link
Author

djsly commented Jul 26, 2017

Thanks @x13n, I will try to find time for this as well, I had a question, how can I know the version of GO used by all of the different k8s projects? when I started to look at fixing, I got stuck at which version of GO do I need :)

@piosz
Copy link
Member

piosz commented Jul 31, 2017

@djsly there is something in godeps https://github.com/kubernetes/autoscaler/blob/master/addon-resizer/Godeps/Godeps.json#L3, though there is not guarantee it was built with this version.

@mwielgus
Copy link
Contributor

@piosz - kubernetes/autoscaler contains the new version that has not been fully release yet. The old one lived in kubernetes/contrib.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 14, 2018
@djsly
Copy link
Author

djsly commented Mar 14, 2018

This is fixed in the latest release, closing.

@djsly djsly closed this as completed Mar 14, 2018
@seh
Copy link

seh commented Aug 15, 2018

Which release is that? I still see this behavior—for both the "tolerations" and "affinity" fields in the pod spec—using the container image k8s.gcr.io/addon-resizer:1.7.

@seh
Copy link

seh commented Aug 15, 2018

Ah, I see there was a release of version 1.8.1 on 8 December 2017.

@seh
Copy link

seh commented Aug 15, 2018

Version 1.8.1 does not parse command-line flags properly (per #559). There is also a later container image k8s.gcr.io/addon-resizer:1.8.3 that's free of that problem.

TeddyAndrieux added a commit to scality/metalk8s that referenced this issue Jun 12, 2019
TeddyAndrieux added a commit to scality/metalk8s that referenced this issue Jun 12, 2019
voelzmo pushed a commit to voelzmo/autoscaler that referenced this issue Nov 22, 2023
* Issue template - autoscaler upstream sync

* corrected CA FAQ and sync request

* typos & 1.x.y->1.x.0

* correct sync-change md
yaroslava-serdiuk pushed a commit to yaroslava-serdiuk/autoscaler that referenced this issue Feb 22, 2024
Rename guaranteed to min and ceiling to max
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/addon-resizer lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

8 participants