[PSUPCLPL-9776] change default podSubnet for IPv6 #174
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
In case of ipv6 usage kubernetes uses /64 for pod subnet per node by default. Accordingly pod subnet for the cluster should be not less than pod subnet per node. Current default podSubnet is fd02::/80 which leads to error during installation procedure.
There are flags for controller-manager which allow to reduce this network but kubeadm fails to run some command during cluster installation. So it's better to use the default kubernetes settings.
Fixes # (issue)
PSUPCLPL-9776
Solution
hash
in case of ipv6 podSubnet (this setting is already described in the installation documentation, but making it default helps to avoid errors in case users don't read all the documentation).How to apply
Deploy cluster in ipv6 network environment.
Test Cases
Deploy cluster in ipv6 network environment.
Check that no errors about podSubnet appear during the installation and calico is up&running.
Deploy cluster with default calico settings in ipv4 environment.
Check that calico-node pods are up&running.
Checklist
Unit tests
Indicate new or changed unit tests and what they do, if any.
Reviewers
@koryaga @iLeonidze @Zaborin @alexarefev @Yaroslav-Lahtachev @dmyar21