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

Medusa: {} leads to a cluster that doesn't progress and doesn't log. #1416

Open
Miles-Garnsey opened this issue Sep 24, 2024 · 0 comments
Open
Labels
bug Something isn't working refactoring

Comments

@Miles-Garnsey
Copy link
Member

Miles-Garnsey commented Sep 24, 2024

What happened?

If (like works with Reaper) you put medusa: {} to configure a default Medusa, the cluster fails to progress, and neither logs nor an error condition on the cluster raise the problem to the user's attention. It just fails silently.

Did you expect to see something different?

We should at least log, reject at the webhook, or add an error status to the cluster when this happens.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-259

@Miles-Garnsey Miles-Garnsey added bug Something isn't working refactoring labels Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working refactoring
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant