How To Customize CoreDNS Configuration for Adding Additional External DNS
Problem
How To Customize CoreDNS Configuration for Adding Additional External DNS.
Environment
Platform9 Managed Kubernetes - v5.2 and K8s v1.20 and Higher
AddOn Management
Procedure
Generate the TOKEN by following steps mentioned in Keystone Identity.
API to retrieve existing CoreDNS ClusterAddon object detail.
curl -X GET -H "X-Auth-Token: $TOKEN" https://<DU_FQDN>/qbert/v4/<PROJECT_ID>/sunpike/apis/sunpike.platform9.com/v1alpha2/namespaces/default/clusteraddons/<CLUSTER_UUID>-coredns$ curl -X GET -H "X-Auth-Token: $TOKEN" https://cs-sanchit.platform9.horse/qbert/v4/1c1003c1b84e47e7bd2a4cdf3b725976/sunpike/apis/sunpike.platform9.com/v1alpha2/namespaces/default/clusteraddons/8c8f1d62-159a-4829-b68f-3432d4a9afc6-coredns | jq
...
...
"spec": {
"clusterID": "8c8f1d62-159a-4829-b68f-3432d4a9afc6",
"version": "1.7.0",
"type": "coredns",
"override": {
"params": [
{
"name": "dnsMemoryLimit",
"value": "170Mi"
},
{
"name": "dnsDomain",
"value": "cluster.local"
}
]
},
"watch": trueCreate a new JSON spec file with the required additional DNS configuration parameter.
This needs to be inputted as a value for the parameter base64EncAdditionalDnsConfig in the JSON spec file.
You can read more about it here CoreDNS Addon.
Patch the existing CoreDNS ClusterAddon object with the newly created Spec file coredns.json.
PreviousDelete a Cluster using the Qbert API
NextHow To Avoid Placement of More Than One Pod Replicas on Same Worker Node
Last updated
