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

Operator fails "silently" to update Superset Cluster's resource #366

Open
Tracked by #383
Maleware opened this issue May 5, 2023 · 0 comments
Open
Tracked by #383

Operator fails "silently" to update Superset Cluster's resource #366

Maleware opened this issue May 5, 2023 · 0 comments

Comments

@Maleware
Copy link
Contributor

Maleware commented May 5, 2023

Affected version

No response

Current and expected behavior

I could recreate the problem when changing the "data" storage size.Changing CPU or Memory resources seems to work (results in a Pod restart)

Possible solution

In order to capture this we either need webhooks or track the resources in the status of the custom resource and delete and recreate the statefulset (PVCs should be resized automatically?)

Additional context

No response

Environment

No response

Would you like to work on fixing this bug?

None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant