jklein
b190b7e833
smb.conf is rendered from samba.shares and mounted with subPath, so adding, renaming or re-scoping a share rewrote the ConfigMap while the running smbd kept its old share list: the pod template was unchanged, nothing restarted, and the kubelet does not refresh subPath mounts. The share simply did not exist for clients while the release looked healthy - the failure mode from #82. The pod template now carries checksum/config over the rendered ConfigMap. users.conf cannot be covered the same way: it comes from a 1Password-backed Secret whose content Helm never sees, and the operator's auto-restart only handles Deployments, not this StatefulSet. values.yaml now documents that limitation and the manual rollout restart it requires. Major bump: runtime behavior changes - a share change now costs a restart of the samba pod, which drops open SMB sessions (share data lives on PVCs and is unaffected).
11 lines
184 B
YAML
11 lines
184 B
YAML
apiVersion: v2
|
|
name: samba
|
|
description: A Helm chart for Samba
|
|
icon: https://avatars.githubusercontent.com/u/13281359
|
|
|
|
type: application
|
|
|
|
version: 5.0.0+up4.23.10
|
|
|
|
appVersion: 4.23.10
|