Skip to content

Extends coredns_autoscaler field in Kubernetes cluster#1153

Open
skumarc-do wants to merge 1 commit into
mainfrom
skumarc/cpa-coredns
Open

Extends coredns_autoscaler field in Kubernetes cluster#1153
skumarc-do wants to merge 1 commit into
mainfrom
skumarc/cpa-coredns

Conversation

@skumarc-do
Copy link
Copy Markdown
Collaborator

@skumarc-do skumarc-do commented Apr 3, 2026

New model: specification/resources/kubernetes/models/coredns_autoscaler.yml

  • Referenced from:
    • models/cluster.yml
    • models/cluster_read.yml
    • models/cluster_update.yml
  • Examples updated in specification/resources/kubernetes/responses/examples.yml where other plugin blocks are shown.

Referenced PRs - digitalocean/godo#986

@skumarc-do skumarc-do force-pushed the skumarc/cpa-coredns branch from 81f74f9 to c47df41 Compare May 15, 2026 05:24
@skumarc-do skumarc-do marked this pull request as ready for review May 15, 2026 05:26
@RohithSangati
Copy link
Copy Markdown

RohithSangati commented May 15, 2026

For all create, update, and delete requests, will the coredns_autoscaler field always be present in the response from now onwards, regardless of whether its value is null or not?

@skumarc-do
Copy link
Copy Markdown
Collaborator Author

For all create, update, and delete requests, will the coredns_autoscaler field always be present in the response from now onwards, regardless of whether its value is null or not?

Yes. The cluster body returned by Create/Update/Get/List always includes coredns_autoscaler (defaults to { "enabled": false }) because publicapi.ToCluster initializes it before serialization, same as the other plugin fields (routing_agent, amd_, nvidia_, rdma_*).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants