Open parveenk27 opened 6 years ago
I've found the similar issue : https://github.com/kubernetes/kubernetes/issues/57673
I found the solution from above mentioned issue, and I think It's a bug in Tectonic installer config.
Change kube-controller-manager
's parameter --horizontal-pod-autoscaler-use-rest-clients
to false
and It works. Actually the issue is, the default value of parameter --horizontal-pod-autoscaler-use-rest-clients
is true
in k8s 1.9.x
.
Any way of getting this to work without re-deploying the cluster?
You could try to edit your cluster's kube-controller-manager
Deployment config and rollout the Deployment.
Yes, I thought about that, but would this actually be persistent across updates?
I'm not sure, But I think it will stay persistent because after all it's a Deployment config and It will be get stored in etcd
.
Oh I'm not worried about that particular scenario - I was thinking of the case where tectonic pushes an update to the hyperkube image. The update agent would need to re-deploy the controller manager using an edited configuration and I'd assume it would therefore overwrite any changes I did to it.
Either way, I'll try adding that config parameter to the deployment - I can always re-add it for now, but I hope that a future update would eliminate the need for it to exist.
Issue Report Template
Tectonic Version
tectonic_1.9.6-tectonic.1
Environment
AWS
Expected Behavior
Actual Behavior
Reproduction Steps
Step 1.
Step 2.
Step 3.
Other Information
I've also checked heapster.