Johannes Kastl<p><rant><br>OK, so however thought up the structure of the <a href="https://digitalcourage.social/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gitlab</span></a> helm chart was ... creative, to put it politely.</p><p>The chart itself has dependencies, as is common with helm charts.<br>But it also has a charts directory, which contains 5 other charts. Including one called gitlab.<br>Which again has a charts directory as well as dependencies.</p><p>So, depending on which chart you want to configure, it might be chart-name.something or gitlab.chart-name.something. Oh, they also use global.something or global.chart-name.something.</p><p>And as this is not creative enough, some charts are installed if chart-name.install is true. For some it is chart-name.enabled...</p><p>But help is near, there is an operator, that does the heavy lifting for you. Oh wait, it uses the values from the helm chart of its CRD...<br></rant></p><p><a href="https://digitalcourage.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitLab</span></a> <a href="https://digitalcourage.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a> <a href="https://digitalcourage.social/tags/helm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>helm</span></a> <a href="https://digitalcourage.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kubernetes</span></a> <a href="https://digitalcourage.social/tags/why" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>why</span></a></p>