[kube-prometheus-stack] Prometheus Operator pod cannot come up when admission hook is disabled

[AndrewSav]

Describe the bug a clear and concise description of what the bug is.

Since https://github.com/prometheus-community/helm-charts/issues/1438 was close by the bot, re-opening it here, please let me know what I need to do to avoid closing it in future. Please refer to prior discussion to https://github.com/prometheus-community/helm-charts/issues/1438 Prometheus Operator pod cannot come up with a missing admission hook secret error if admission hook is disabled.

What's your helm version?

v3.7.0

What's your kubectl version?

v1.22.2

Which chart?

kube-prometheus-stack

What's the chart version?

19.0.2

What happened?

The operator pod cannot come up, with the following error message: MountVolume.SetUp failed for volume "tls-secret" : secret "prometheus-kube-prometheus-admission" not found. This message is displayed because admission hook is disabled and the secret is not present.

What you expected to happen?

I expect the operator to come up.

How to reproduce it?

Install the chart with the values below

Enter the changed values of values.yaml?

prometheusOperator:
  admissionWebhooks:
    enabled: false

Enter the command that you execute and failing/misfunctioning.

helm install prometheus prometheus-community/kube-prometheus-stack -n monitoring -f prometheus-values.yaml

Anything else we need to know?

No response

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[AndrewSav]

I believe this is still happening

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[AndrewSav]

recent activity

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[AndrewSav]

recent activity

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[AndrewSav]

recent activity

[AndrewSav]

I'm not sure what I need to do to provide "further activity" so that the bot removes the stale label

[nicl-dev]

Is anyone still working on this? Can we get a review on the PR? I would like to avoid managing the secret manually for each cluster we have. @andrewgkew @gianrubio @gkarthiks @scottrigby @Xtigyro

[Vsevosemnog]

Need solution too(

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[AndrewSav]

This is a message to indicate that people are still interested in this issue and generate "recent activity"

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[nicl-dev]

This is a message to indicate that people are still interested in this issue and generate "recent activity".

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[nicl-dev]

Not stale.

[AndrewSav]

So sometimes the bot remove the label straight away, and sometimes it does not. I suspect that a) there is some message length requirement to trigger the bot, and b) message uniqueness may be?

[tsloughter]

I'm seeing this too and operator is unable to come up.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[nicl-dev]

Still relevant.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[InCogNiTo124]

I have the same behaviour

[stale[bot]]

This issue is being automatically closed due to inactivity.