Expect surge in running pods and avoid redis public expose #646
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Service to access directly master and slaves instances in Redis was added in #627, This exposes the service publicly using loadBalancers.
To make it security by default the service is changed to only expose internally in the cluster. Let the user to create their ow service if exposing publicly is the option until its available in the operator by a config set.
Running pods can surge the number of expected replicas during rollouts of a deployment change in sentinels, while a new version of the template is deployed. In anycase we will always consider not running while there are pods terminating or pending .