Managed Kubernetes
Latest
Frequently Asked Questions
Solutions
How Tos
Internal Only
Templates
Powered By

Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Adding new node fails with error "Error registering network: failed to acquire lease: out of subnets"
Copy Markdown
Open in ChatGPT
Open in Claude
Problem
- Adding new node fails & flannel shows below error:
Bash
{"log":"E0516 23:16:46.941582 1 main.go:293] Error registering network: failed to acquire lease: out of subnets\n","stream":"stderr","time":"2023-05-16T23:16:46.94167563Z"}Environment
- Platform9 Managed Kubernetes- v5.4 and Higher.
- Cluster configured with flannel.
- The node is re-added to the cluster.
Cause
- Flanneld by default sets a TTL for each key in etcd. The default TTL is however 24 hours. So, the subnet is released after 24 hours and new nodes can be added then.
Resolution
- Check the current TTL value using the command below:
Bash
# /opt/pf9/pf9-kube/bin/etcdctl --cacert=/etc/pf9/kube.d/certs/etcdctl/etcd/ca.crt --cert=/etc/pf9/kube.d/certs/etcdctl/etcd/request.crt --key=/etc/pf9/kube.d/certs/etcdctl/etcd/request.key get /coreos.com/network/subnets/10.244.72.1-24- Default TTL value is set to 24 hours and re-adding/adding nodes should work after this TTL expiry after which the unused subnets would be released.
VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches
Last updated on
Was this page helpful?
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message