Skip to content
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

Dual Stack Support #439

Open
Tracked by #549
majst01 opened this issue Dec 2, 2024 · 0 comments
Open
Tracked by #549

Dual Stack Support #439

majst01 opened this issue Dec 2, 2024 · 0 comments

Comments

@majst01
Copy link
Contributor

majst01 commented Dec 2, 2024

Upstream References:

The main difference is that now the insfrastructure extension can put the Cidrs of workers/pods/services into the Status of the Infrastructure Resource. In The Shoot Spec only the IPFamilies which should be used must be specified:


kind: Shoot
apiVersion: core.gardener.cloud/v1beta1
metadata:
  ...
spec:
  ...
  networking:
    type: ...
    pods: 192.168.128.0/17 # optional
    nodes: 192.168.0.0/18 # optional
    services: 192.168.64.0/18 # optional
    ipFamilies:
      - IPv4
      - IPv6

See THE AWS Extension for reference: https://github.com/gardener/gardener-extension-provider-aws/blob/master/docs/usage/ipv6.md and

kube-controller-manager

must be configured that he adds both AFs to the node like:

--node-cidr-mask-size-v4=23
--node-cidr-mask-size-v6=80 # see https://github.com/gardener/gardener/blob/master/pkg/component/kubernetes/controllermanager/controllermanager.go#L676
--allocate-node-cidrs=true
--cluster-cidr=10.244.128.0/18, 2001:db8::/64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant