Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP panic when toggling spec.storage.tls.enabled to true, when using Tempo with AWS STS #1067

Closed
rubenvp8510 opened this issue Oct 19, 2024 · 0 comments

Comments

@rubenvp8510
Copy link
Collaborator

When we set spec.storage.tls.enabled to true, using Tempo with AWS STS, we get the following error and the changes are not applied.

error: tempostacks.tempo.grafana.com "tmstack" could not be patched: Internal error occurred: failed calling webhook "vtempostack.tempo.grafana.com": failed to call webhook: Post "https://tempo-operator-controller-service.openshift-tempo-operator.svc:443/validate-tempo-grafana-com-v1alpha1-tempostack?timeout=10s": EOF
You can run `oc replace -f /var/folders/v_/xjhg70nn5h9g__sf8d7wg99r0000gn/T/oc-edit-307932674.yaml` to try this update again.

Steps to reproduce the issue:

  • Install the Tempo operator on a STS enabled OCP cluster.
    
  • Create a Tempo instance with AWS STS. 
    
  • Set the spec.storage.tls.enabled to true in the TempoStack CR.
    
  • The change will not be applied with the above errors in description.
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant