TLS configuration unavailable in helm chart values

[r0bj]

What happened:
According to the changelog, custom TLS configuration was added in Helm chart version 3.8.3. I can see the TLS configuration in the values.yaml file on the master branch here. However, it’s unavailable in the latest Helm chart I downloaded, which is version 3.12.2:

$ helm repo add metrics-server https://kubernetes-sigs.github.io/metrics-server/
$ helm repo update
$ helm show values metrics-server/metrics-server --version 3.12.2 | grep -i 'tls:'
<empty>

What you expected to happen:
The custom TLS configuration should be available in the latest Helm chart. As far as I know, it should have been available since version 3.8.3.

/kind bug

[richabanker]

/triage accepted
/assign @stevehipwell

[stevehipwell]

@r0bj the Helm chart is released from the release branches. If you look at the CHANGELOG on master you'll see the TLS config is unreleased.

[steinwelberg]

When is the chart going to be released? The MR was merged over half a year ago.

[stevehipwell]

@steinwelberg the chart release process is documented. The primary driver is still an issue being opened and triaged, although it's actually more complicated now as the release has to come off a release branch. This is exactly the same as for how code merged to master gets released.

[cwrau]

@steinwelberg the chart release process is documented. The primary driver is still an issue being opened and triaged, although it's actually more complicated now as the release has to come off a release branch. This is exactly the same as for how code merged to master gets released.

Not to be majorly off-topic, but what prevents metrics-server from being released more often? Why wait on issues instead of just releasing more often? 🤔

We could've had this feature released nearly a year ago and would just release a new version when the mentioned issue has been fixed

[stevehipwell]

Not to be majorly off-topic, but what prevents metrics-server from being released more often? Why wait on issues instead of just releasing more often? 🤔

@cwrau the current release process is time consuming as it requires code to be moved to a release branch which results in a chart change taking multiple PRs.

We could've had this feature released nearly a year ago and would just release a new version when the mentioned issue has been fixed

Anyone is welcome to open a chart release issue as is documented in the chart release process.

Moving forward I've opened #1715 to simplify the chart release process as we only "need" to release the chart off a release branch if the chart has been modified to be incompatible with the target version.