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.
This pull request introduces changes to the Bitwarden chart to allow users to configure the number of replicas for each component from the values.yaml file. By default, the number of replicas is set to one for all components. However, the Bitwarden documentation suggests increasing the number of replicas to enhance high availability, which is currently not possible with the existing configuration. This update aims to provide flexibility in setting the replica count per component directly from the values.yaml file.
Changes Made
Replicas Configuration:
Introduced new fields in the values.yaml file to specify the number of replicas for each component.
Updated deployment templates to use the specified replica count from the values.yaml file instead of defaulting to one.
Job Adaptation:
Modified the job configuration to consider only the state of the first container set to true. This adaptation ensures that the job correctly handles the state with the increased number of replicas.