danhuawang commented on code in PR #9292: URL: https://github.com/apache/gravitino/pull/9292#discussion_r2591181271
########## dev/charts/gravitino/values.yaml: ########## @@ -556,3 +556,76 @@ tolerations: [] ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity ## affinity: {} + +## PodDisruptionBudget configuration +## PodDisruptionBudgets limit the number of pods that can be down simultaneously during voluntary disruptions +## (such as node drains, cluster upgrades, or pod evictions), ensuring high availability and service continuity. +## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/ +## +podDisruptionBudget: + ## @param podDisruptionBudget.enabled Enable PodDisruptionBudget creation + ## Set to true to create a PodDisruptionBudget resource for the Gravitino deployment + ## + enabled: false + + ## @param podDisruptionBudget.minAvailable Minimum number/percentage of pods that must remain available + ## Specify either an integer (e.g., 1, 2) or a percentage string (e.g., "50%") + ## This ensures at least this many pods stay running during voluntary disruptions + ## + ## Examples: + ## minAvailable: 1 # At least 1 pod must remain available + ## minAvailable: 2 # At least 2 pods must remain available + ## minAvailable: "50%" # At least 50% of pods must remain available + ## + ## When to use minAvailable: + ## - Use when you want to guarantee a minimum number of pods stay running + ## - Recommended for production deployments to ensure service availability + ## - With single replica (replicas: 1), minAvailable: 1 prevents all voluntary disruptions + ## - With multiple replicas, allows disruptions while maintaining minimum availability + ## + minAvailable: 1 Review Comment: Add comment, but the default value minAvailable: 1 is more meaningful for product deployment. I keep this default value. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
