After upgrade 1.12 to 1.14, /srv/kubernetes directory was removed.

[Seyeong Kim]

This is the customer's issue.

They upgrade cdk from 1.12 to 1.14.

After that, they found out /srv/kubernetes directory was removed.

Because nginx refer to /srv/kubernetes for cert files, service was down.

[George Kraft (cynerva)]

Can you tell us more about their deployment? Is kubeapi-load-balancer colocated with another unit on the same machine?

I ask because kubernetes-master and kubernetes-worker both delete /srv/kubernetes [1][2] on charm upgrade, and this seems like the most likely explanation.

[1]: https://github.com/charmed-kubernetes/charm-kubernetes-master/blob/28610d903ac798b3f9df4897b8f5d8bf9652e9fe/reactive/kubernetes_master.py#L269
[2]: https://github.com/charmed-kubernetes/charm-kubernetes-worker/blob/1006bb62681be7f7a74e90e2c3d7401afffb51c4/reactive/kubernetes_worker.py#L194

[Seyeong Kim (seyeongkim)]

Right, I checked the customer's env

then I found out that kubernetes-master and kubeapi-load-balance unit are in the same node each.

I let them do below to regenerate it

juju config kubeapi-load-balancer extra_sans="IP_OF_LB"
juju config kubeapi-load-balancer extra_sans=""

and it was regenerated.

Is this fixable?

[George Kraft (cynerva)]

> Is this fixable?

Yeah. We can remove the lines from kubernetes-master and kubernetes-worker that delete /srv/kubernetes. That's old upgrade code that's no longer relevant today - it was added over 2 years ago, and predates general availability of CDK.

[Tim Van Steenburgh (tvansteenburgh)]

https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/5
https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/11

[George Kraft (cynerva)]

PRs to stable:
https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/22
https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/13