Add ability to set scheme for probes

[mbasha86]

Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.

Per in-cluster instructions https://headlamp.dev/docs/latest/installation/in-cluster/tls, it mentioned that "Headlamp supports optional TLS termination at the backend server". However, upon doing all required configurations, we found out that the Headlamp container is failing as liveness/readiness probes is sending http request to https server. This is because liveness/readiness probes in headlamp deployment are using default (HTTP) scheme.

Describe the solution you'd like

The ability to set scheme for probes via values.yaml file.

What users will benefit from this feature?

Helm chart users / In-Cluster users

Are you able to implement this feature?

[Yes (I will propose a PR later on ) ]

Do you want to help implement this feature? Please see our contribution docs. For any non-trivial contributions, we advise you to join our our slack channel to discuss the implementation with Headlamp's core developers.

Additional context

[If needed, add any other context or screenshots about the feature request here.]

[tiborauer]

I want to upvote this request.

[scottmbaker]

Hello, I'm experiencing the same issue and I have verified that PR #4478 resolves it for me. I was hoping I could get some insight into the timeline:

1. When is this PR expected to merge?

2. Will it make the next release?

3. When is the next release expected?

Thanks, Scott.

[illume]

@scottmbaker thanks for verifying that. There's a roughly one month release cycle. Next release will probably fall around the end of month (but an exact date hasn't been decided yet).