You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
do not leak api-server cluster ip from seed to shoot (gardener#10949)
* fix: do not leak api-server cluster ip from seed to shoot
* Apply suggestions from code review
new lines etc.
Co-authored-by: Johannes Scheerer <johannes.scheerer@sap.com>
Co-authored-by: Rafael Franzke <rafael.franzke@sap.com>
* refactor: remove unused func
* refactor: remove unnecessary const
* refactor: move seed range check from shoot to cidr
* docs: add reserved ranges to shoot networking guide
* refactor: rename ReservedSeedServiceRange => ReservedKubeApiServerMappingRange
* feat: add IsIPv4, IsIPv6 helper functions to cidr
---------
Co-authored-by: Johannes Scheerer <johannes.scheerer@sap.com>
Co-authored-by: Rafael Franzke <rafael.franzke@sap.com>
| IPv4 | 192.168.123.0/24 | Default VPN Range | Used for communication between seed API server and shoot resources via VPN. Will be removed once feature gate `NewVPN` is graduated. |
96
+
| IPv6 | fd8f:6d53:b97a:1::/96 | Default VPN Range ||
97
+
| IPv4 | 240.0.0.0/8 | Kube-ApiServer Mapping Range | Used for the `kubernetes.default.svc.cluster.local` service in a shoot |
98
+
99
+
> :warning: Do not use any of the CIDR ranges mentioned above for any of the node, pod or service networks.
100
+
> Gardener will prevent their creation. Pre-existing shoots using reserved ranges will still work, though it is recommended
101
+
> to recreate them with compatible network ranges.
0 commit comments