Reaper Operator Helm Chart
Provisions the Reaper for Apache Cassandra component
|K8ssandra Team||[email protected]||https://github.com/k8ssandra|
||Replaces the chart name which is used in the metadata.name of objects created by this chart.|
||Replaces the value used for metadata.name in objects created by this chart. The default value has the form releaseName-chartName.|
||Labels to be added to all deployed resources|
||Sets the number of reaper-operator pods.|
||Container repository where the reaper-operator resides|
||Pull policy for the operator container|
||Tag of the reaper-operator image to pull from image.repository|
||References to secrets to use when pulling images. ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/|
||Annotations for the reaper-operator service account.|
||Annotations for the reaper-operator pod.|
||PodSecurityContext for the reaper-operator pod.|
||Mark root filesystem as read only|
||Run reaper-operator container as non-root user|
||Group for the user running the reaper-operator container / process|
||User for running the reaper-operator container / process|
||Resources requests and limits for the cass-operator pod. We usually recommend not to specify default resources and to leave this as a conscious choice for the user. This also increases chances charts run on environments with little resources, such as Minikube. If you do want to specify resources, uncomment the following lines, adjust them as necessary, and remove the curly braces after ‘resources:’. limits: cpu: 100m memory: 128Mi requests: cpu: 100m memory: 128Mi|
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified March 5, 2021: Update size up/down example (#493) (c515698)