-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[bitnami/redis] Do not create master and replica serviceaccounts when using sentinel #22716
Conversation
Not relevant, solved in #22223 |
Is this PR a duplicate of #22223 ? |
Hi @wilmardo, Thanks for the contribution!! Could you check the conflicts? |
b6f5cde
to
8c72700
Compare
4a75994
to
6d028a4
Compare
…sing sentinel Signed-off-by: wilmarguida <[email protected]>
6d028a4
to
4d535e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @wilmardo,
Thanks for the contribution!!! LGTM!!
Co-authored-by: Ibone González Mauraza <[email protected]> Signed-off-by: Wilmar den Ouden <[email protected]>
Signed-off-by: Ibone González Mauraza <[email protected]>
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account).
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]>
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]>
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]>
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]>
Since 18.8.3 (#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]>
… using sentinel (bitnami#22716) * fix(redis): skip creation of master and replica serviceaccount when using sentinel Signed-off-by: wilmarguida <[email protected]> * chore(redis): bump the chart version Co-authored-by: Ibone González Mauraza <[email protected]> Signed-off-by: Wilmar den Ouden <[email protected]> --------- Signed-off-by: wilmarguida <[email protected]> Signed-off-by: Wilmar den Ouden <[email protected]> Signed-off-by: Ibone González Mauraza <[email protected]> Co-authored-by: Ibone González Mauraza <[email protected]> Co-authored-by: Ibone González Mauraza <[email protected]>
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]>
… using sentinel (bitnami#22716) * fix(redis): skip creation of master and replica serviceaccount when using sentinel Signed-off-by: wilmarguida <[email protected]> * chore(redis): bump the chart version Co-authored-by: Ibone González Mauraza <[email protected]> Signed-off-by: Wilmar den Ouden <[email protected]> --------- Signed-off-by: wilmarguida <[email protected]> Signed-off-by: Wilmar den Ouden <[email protected]> Signed-off-by: Ibone González Mauraza <[email protected]> Co-authored-by: Ibone González Mauraza <[email protected]> Co-authored-by: Ibone González Mauraza <[email protected]> Signed-off-by: Jose Antonio Carmona <[email protected]>
Since 18.8.3 (bitnami#22716) no service account is created with architecture set to standalone. In this case the serviceaccount and application condition didn't match for master (instead the condition for replicas was used for the master service account). Signed-off-by: Wout Van De Wiel <[email protected]> Signed-off-by: Jose Antonio Carmona <[email protected]>
Description of the change
Currently when choosing to use sentinel you get all the serviceaccounts not just the one needed.
Currently is creates the master and replica service accounts:
Benefits
Less clutter, removes unneeded resources. More inline with the other resources in the
master/
andreplica/
template folder. They all have this if check, this is the one resource where it was missing.Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm