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

kubernetes-master juju layer registry action breaks nginx configmap #44920

jacekn opened this Issue Apr 25, 2017 · 0 comments


None yet
1 participant

jacekn commented Apr 25, 2017

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): nginx-load-balancer-conf


Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:33:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}


  • Cloud provider or hardware configuration: OpenStack
  • OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS
  • Kernel (e.g. uname -a): 4.4.0-71-generic #92-Ubuntu SMP Fri Mar 24 12:59:01 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools: juju
  • Others:

What happened:

I used the "registry" action to create docker registry inside the cluster. It modified nginx-load-balancer-conf config map. It replaced:

body-size: 1024m

with (incorrect):

max-body-size: 1024m

What you expected to happen:

Expected ConfigMap to stay as it was

How to reproduce it (as minimally and precisely as possible):

Deploy cluster with juju and then use "registry" action to create docker registry

Anything else we need to know:

sttts pushed a commit to sttts/kubernetes that referenced this issue Apr 28, 2017

Merge pull request kubernetes#44921 from jacekn/registry-fix
Automatic merge from submit-queue (batch tested with PRs 42432, 44628, 45101, 44921)

Use correct option name in the kubernetes-worker layer registry action

**What this PR does / why we need it**: It fixes kubernetes#44920 

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes kubernetes#44920 

**Special notes for your reviewer**:

**Release note**:

Ensure kubernetes-worker juju layer registry action uses correct ingress controller option name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment