Skip to content
This repository has been archived by the owner on Dec 21, 2021. It is now read-only.

Allow configuration of Pod CIDR Range #49

Closed
lfrancke opened this issue Feb 10, 2021 · 1 comment · Fixed by #50
Closed

Allow configuration of Pod CIDR Range #49

lfrancke opened this issue Feb 10, 2021 · 1 comment · Fixed by #50
Assignees
@soenkeliebau
Milestone
Release #1

Comments

@lfrancke
Copy link
Member

We don't use it but Krustlet defaults to use one.
We need to disable it to not cause issues:
@lfrancke lfrancke added this to the Milestone #1 milestone Feb 10, 2021
@lfrancke
Copy link
Member Author

It seems as if setting the value to an empty strings works and allows the apiserver to assign a valid range.

@lfrancke lfrancke linked a pull request Feb 10, 2021 that will close this issue
Adds command line parameter to control the pod cidr the agent requests from Kubernetes #50
Merged
soenkeliebau added a commit that referenced this issue Feb 11, 2021
@soenkeliebau
Adds command line parameter to control the pod cidr the agent request…
6c1f260 
…s from Kubernetes (#50)

Currently this is hardcoded to a value that can cause issues. This PR changes the default value to an empty string which causes Kubernetes to assign a valid range. 
Additionally a config parameter has been added to configure this if needed.

fixes #49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@soenkeliebau soenkeliebau

Labels
None yet
Projects
None yet
Milestone
Release #1
2 participants
@lfrancke @soenkeliebau