Remove deployment anti affinity rule. #9
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.
Description
I don't think this is required for this extension and it's somehow creating a burden on local setups because for some reason it always deploys 2 replicas even when passing 1 explicitly through the chart values. So, for single node seeds the extension will not become ready.
Only Gardener provider extensions have these constraints anyway, so I think we can just remove. It's not a problem when this extension is not available for a short time.