-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
StatefulSet Support for Updating Volume Claim Template #4650
Comments
/sig storage |
@huww98: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/sig apps |
This feature is highly anticipated and we eagerly await its implementation. |
A few of the yk8s config settings in `k8s-service-layer.prometheus` and `k8s-service-layer.rook` are actually immutable because they feed into the currently immutable `volumeClaimTemplate` field of Kubernetes objects. Example: The `k8s-service-layer.prometheus.thanos_storegateway_size` yk8s config setting feeds into the `storegateway.persistence.size` parameter of the bitnami/thanos helm chart which feeds into the `volumeClaimTemplate` field of the `thanos-storegateway` statefulset created. That field is currently immutable making helm updates with the parameter fail. Related-to: kubernetes/enhancements#4650
The `k8s-service-layer.prometheus.thanos_storegateway_size` yk8s config setting feeds into the `storegateway.persistence.size` parameter of the bitnami/thanos helm chart which feeds into the `volumeClaimTemplates` field of the `thanos-storegateway` statefulset created. That field is currently immutable making helm updates with the parameter fail. Related-to: kubernetes/enhancements#4650
A few of the yk8s config settings in `k8s-service-layer.prometheus` and `k8s-service-layer.rook` are actually immutable because they feed into the currently immutable `volumeClaimTemplate` field of Kubernetes objects. Example: The `k8s-service-layer.prometheus.thanos_storegateway_size` yk8s config setting feeds into the `storegateway.persistence.size` parameter of the bitnami/thanos helm chart which feeds into the `volumeClaimTemplate` field of the `thanos-storegateway` statefulset created. That field is currently immutable making helm updates with the parameter fail. Related-to: kubernetes/enhancements#4650
A few of the yk8s config settings in `k8s-service-layer.prometheus` and `k8s-service-layer.rook` are actually immutable because they feed into the currently immutable `volumeClaimTemplate` field of Kubernetes objects. Example: The `k8s-service-layer.prometheus.thanos_storegateway_size` yk8s config setting feeds into the `storegateway.persistence.size` parameter of the bitnami/thanos helm chart which feeds into the `volumeClaimTemplate` field of the `thanos-storegateway` statefulset created. That field is currently immutable making helm updates with the parameter fail. Related-to: kubernetes/enhancements#4650
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
A few of the yk8s config settings in `k8s-service-layer.prometheus` and `k8s-service-layer.rook` are actually immutable because they feed into the currently immutable `volumeClaimTemplate` field of Kubernetes objects. Example: The `k8s-service-layer.prometheus.thanos_storegateway_size` yk8s config setting feeds into the `storegateway.persistence.size` parameter of the bitnami/thanos helm chart which feeds into the `volumeClaimTemplate` field of the `thanos-storegateway` statefulset created. That field is currently immutable making helm updates with the parameter fail. Related-to: kubernetes/enhancements#4650
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: