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?
How To Persist Changes to CoreDNS ConfigMap on PMK Cluster
Copy Markdown
Open in ChatGPT
Open in Claude
Problem
Changes made to the CoreDNS ConfigMap do not persist after pf9-kube service restart.
Environment
- Platform9 Managed Kubernetes - v5.1 and K8s v1.19 and Lower
- CoreDNS
Answer
- When the pf9-kube service is restarted on the master nodes, the CoreDNS configurations are re-applied using the default template to ensure that resources are consistent.
- This is achieved by applying the template file
/opt/pf9/pf9-kube/conf/addons/dns/coredns.yamlwhen kubectl apply is run during service startup. - In order to make the changes made to CoreDNS configMap persist across the pf9-kube service restarts you can make the changes to the existing CoreDNS configMap as well as to the files
/opt/pf9/pf9-kube/conf/addons/dns/coredns.yamland/etc/pf9/kube.d/addons/dns/coredns.yamlrespectively.
This will NOT ensure that the changes persist across the cluster upgrades. The changes will persist only across the service restarts.
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