Closed gberche-orange closed 2 years ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
Bug Report
What happened:
When setting
controllerManager.replicas=3
during ahelm upgrade
command, then the controllerManager Deployment replicas is observed to remain at 1 (its default value)https://github.com/kubernetes-sigs/service-catalog/blob/880e4007005c6848c6720150f5269499071cfbad/charts/catalog/values.yaml#L51-L52
After much debugging effort, the Deployment.replica is actually modified by the migration job documented at https://github.com/kubernetes-sigs/service-catalog/blob/master/docs/migration-apiserver-to-crds.md which outputs the following traces
and actually scaling up the replicas to the hard coded 1 value
https://github.com/kubernetes-sigs/service-catalog/blob/7942106ffe59d1579c33fff573dd20376e242887/pkg/migration/scale.go#L53-L56
What you expected to happen:
The controllerManager Deployment replica to be set to 3 regardless of the
helm install
orhelm upgrade
command be executedHow to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
This seems to relate to https://github.com/kubernetes-sigs/service-catalog/issues/2853
Environment: