Nic Roland :mastodon:<p>Helm charts are great for managing applications but a massive pain to prep for initial deployment, am I doing this wrong?</p><p>With a new chart, I spend time reading through chart values and reading over the templates to see if certain features are supported by the chart or not. Reading go templates isn't exactly how I enjoy spending my time</p><p>When you create a chart, the default template supports a lot of standard features (overriding labels, setting TLS details for the ingress, securityContext, etc) which is fantastic... When I find a ready made chart on GitHub, I find that people have renamed some of these or stripped them out. I'm using NFS storage which means I think about process UID/GID a lot and typically create PVCs manually to be mounted in specific places which sometimes works great and sometimes not so much</p><p>I feel like I missed the boat with k8s-at-home which had an incredible collection of ready-made charts but it's a shame it's gone dark since :sadness: </p><p><a href="https://techhub.social/tags/helm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>helm</span></a> <a href="https://techhub.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kubernetes</span></a> <a href="https://techhub.social/tags/k8s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>k8s</span></a> <a href="https://techhub.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a> <a href="https://techhub.social/tags/selfhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhost</span></a></p>