CoreDNS operator:- Addition of list of features

[Abhik1998]

Description:-
(GSOC proposal 2020)
We have some new features to be added this time to the CoreDNS operator.The current operator is a proof of concept of the add-on library.

Goal:-
Define the set of milestones and criteria for productionizing the CoreDNS operator. The current operator is a proof of concept of the add-on library. The goal of the alpha operator is to provide a minimal feature set that is manageable, predictable, and reliable in a production environment.

• Implement CoreDNS - operator smoke test.
  Implementing and validating various scenarios like creation, deletion, configuration change, etc.
  This work will require adding multiple versions to the CoreDNS version directory. Issue
• Provide metrics in the kubebuilder-declarative-pattern library
  A user should be able to emit metrics on the Prometheus metrics endpoint. Metrics should be written to the controller-runtime Prometheus Registry. Issue
• Integrate Kustomize with kubebuilder-declarative-pattern
  Finish and share design doc. Issue
• Implement rolling updates for ConfigMap
  Rolling update for Configs should use hashed names (kustomize supports this) Issue

Proposed mentors: Jeff Johnson [ @johnsonj ]

[dholbach]

CCing @rajansandeep

[dholbach]

@rajansandeep and @johnsonj

Looks like @Abhik1998 got the proposal added to /cncf/soc as a project - do you feel the project description above makes sense? Does this capture the ideal outcome for the operator? I feel like some coordination and planning with the coredns team about this operator should be part of this project too.

[Abhik1998]

@dholbach I hope this description helps. I have updated that.

[johnsonj]

Totally agree @dholbach - It'd be great to get their input and buy in. Our ultimate goal is to have an 'alpha quality' operator for managing CoreDNS in the cluster and they're the experts on what that really means.

@rajansandeep Can you check out this doc for more context and let me know what you think?

[rajansandeep]

@rajansandeep Can you check out this doc for more context and let me know what you think?

@johnsonj The goals set in the doc for an 'alpha quality' operator seems reasonable to me.
The only addition which comes to mind right now is whether we would want to add the CoreDNS corefile migration support while upgrading/downgrading the CoreDNS version. (This is already been done for kubeadm)

I'd like to kick off progress for the CoreDNS operator by updating it to v2 (I was to do it some time ago, but was absent due to a long vacation), which will also cover the remaining work in #27 (comment)

[Raman-Kumar]

@rajansandeep
Can you suggest me some docs or resources to properly understand the codebase of cluster-addons and contributing to it?

[johnsonj]

The README in this project (cluster-addons) should cover a bit of the high-level ideas. The README for the CoreDNS operator primarily covers 'how we got to this point'.

For more information on the frameworks the operator builds on:

• kubebuilder book
• kubebuilder-declarative-pattern repo / docs & kubecon talk

If the timing works for you, we have a bi-weekly meeting (see 'Cluster Addons')

[johnsonj]

@Abhik1998 thank you for kicking off the organization of this! I duplicated this issue as #47 so that I could have edit access. I'm going to dupe this bug to that to keep things clear.

[johnsonj]

/dupe #47

[johnsonj]

/close

[k8s-ci-robot]

@johnsonj: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.