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

Many Pravega Spec parameters are still not updatable at runtime #557

Closed
SrishT opened this issue Jun 10, 2021 · 0 comments · Fixed by #561
Closed

Many Pravega Spec parameters are still not updatable at runtime #557

SrishT opened this issue Jun 10, 2021 · 0 comments · Fixed by #561

Comments

@SrishT
Copy link
Contributor

SrishT commented Jun 10, 2021

Description

There are many Pravega Spec parameters still remaining which cannot be updated once the pravega cluster has been created. All the spec fields other than the the version, replica count, DNS name, JVM options as well as the pravega options still come under this category. While not allowing updates on some parameters might make sense, it will be necessary to allow updates to a few others including controllerResources, segmentStoreResources, segmentStoreEnvVars, segmentStoreSecret etc.

Importance

must have

Location

pkg/controller/pravegacluster/pravegacluster_controller.go

Suggestions for an improvement

The operator reconcile logic would need to be modified so that updates to necessary fields are allowed during the lifetime of the cluster.
A maintenance mode can be added to stop operator from watching all resources and allow the user to make any changes to recover the cluster.

@SrishT SrishT changed the title Many Pravega Spec parameters are still updatable at runtime Many Pravega Spec parameters are still not updatable at runtime Jun 10, 2021
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

Successfully merging a pull request may close this issue.

1 participant