-
Notifications
You must be signed in to change notification settings - Fork 113
Closed
Labels
area/control-planeControl plane relatedControl plane relatedkind/bugBugBugplatform/awsAmazon web services platform/infrastructureAmazon web services platform/infrastructurepriority/1Priority (lower number equals higher priority)Priority (lower number equals higher priority)status/closedIssue is closed (either delivered or triaged)Issue is closed (either delivered or triaged)
Description
How to categorize this issue?
/area control-plane
/kind bug
/platform aws
/priority 1
What happened:
Similar to #619:
On Shoot creation the Network gets created with:
spec:
podCIDR: 100.64.0.0/12
providerConfig:
apiVersion: calico.networking.extensions.gardener.cloud/v1alpha1
backend: none
ipv4:
mode: Never
kind: NetworkConfig
serviceCIDR: 100.104.0.0/13
type: calicoAfter reconciliation the providerConfig gets removed.
spec:
podCIDR: 100.64.0.0/12
serviceCIDR: 100.104.0.0/13
type: calicoWhat you expected to happen:
Not the above one.
How to reproduce it (as minimally and precisely as possible):
See above.
Anything else we need to know?:
Environment:
- Gardener version (if relevant):
- Extension version:
v1.38.1 - Kubernetes version (use
kubectl version): - Cloud provider or hardware configuration:
- Others:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/control-planeControl plane relatedControl plane relatedkind/bugBugBugplatform/awsAmazon web services platform/infrastructureAmazon web services platform/infrastructurepriority/1Priority (lower number equals higher priority)Priority (lower number equals higher priority)status/closedIssue is closed (either delivered or triaged)Issue is closed (either delivered or triaged)