Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

Fix snap configuration not properly handling boolean false values #10

Merged
merged 1 commit into from
Jun 28, 2017

Conversation

Cynerva
Copy link

@Cynerva Cynerva commented Jun 27, 2017

Fixes https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/314

The resultings args file for kubelet looks like this, for example:

--address "0.0.0.0"
--allow-privileged
--anonymous-auth=false
--client-ca-file "/root/cdk/ca.crt"
--cluster-dns "10.152.183.10"
--cluster-domain "cluster.local"
--kubeconfig "/root/cdk/kubeconfig"
--logtostderr
--network-plugin "cni"
--port 10250
--require-kubeconfig
--tls-cert-file "/root/cdk/server.crt"
--tls-private-key-file "/root/cdk/server.key"
--v 0

@Cynerva
Copy link
Author

Cynerva commented Jun 27, 2017

I manually tested this change in a live deployment. Cluster came up fine and e2e passed with no failures. Verified kubelet was started with --anonymous-auth=false.

For automated testing, my plan is to add a validator to our CDK integration tests in a separate PR.

@ktsakalozos
Copy link

LGTM +1 thank you!

@ktsakalozos ktsakalozos merged commit 0fea5cc into rye/snaps Jun 28, 2017
@Cynerva Cynerva deleted the gkk/fix-boolean-false branch June 28, 2017 20:52
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this pull request Jul 3, 2017
…ices

Automatic merge from submit-queue (batch tested with PRs 48439, 48440, 48394)

Fix kubernetes charms not restarting services after snap upgrades

**What this PR does / why we need it**:

This fixes a problem where the Kubernetes charms don't restart services after upgrading snaps. This can cause certain fixes not to be picked up (for example juju-solutions/release#10)

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

**Special notes for your reviewer**:

**Release note**:

```release-note
Fixed kubernetes charms not restarting services after snap upgrades
```
tvansteenburgh pushed a commit to charmed-kubernetes/charm-kubernetes-control-plane that referenced this pull request Apr 1, 2019
…ices

Automatic merge from submit-queue (batch tested with PRs 48439, 48440, 48394)

Fix kubernetes charms not restarting services after snap upgrades

**What this PR does / why we need it**:

This fixes a problem where the Kubernetes charms don't restart services after upgrading snaps. This can cause certain fixes not to be picked up (for example juju-solutions/release#10)

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

**Special notes for your reviewer**:

**Release note**:

```release-note
Fixed kubernetes charms not restarting services after snap upgrades
```
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants