search

kubernetes-sigs / cluster-addons

Addon operators for Kubernetes clusters.
Apache License 2.0
155 stars 47 forks source link

[tracking bug] CoreDNS Operator #47

Closed johnsonj closed 3 years ago

johnsonj commented 4 years ago

Description CoreDNS Operator aims to manage the lifecycle of the CoreDNS installation in the cluster. It is concerned with the installation, updating, and configuration of CoreDNS.

Project 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.

johnsonj commented 4 years ago

Pulling in the content from @Abhik1998 's issue #40

vanou commented 4 years ago

Hello. I would like to work on issues listed here. Can I work on them till GSoC 2020 starts? Or, because these issues are registered as GSoC 2020, there is no way to work on them?

Abhik1998 commented 4 years ago

@vanou I will be working upon them.

vanou commented 4 years ago

@Abhik1998 I understand. Sorry for worrying.

eloyekunle commented 4 years ago

@Abhik1998 Projects are open to all interested GSoC participants. Only when your proposal is accepted by the organization will you be working on it.

Abhik1998 commented 4 years ago

@eloyekunle you are right but @vanou is not a GSoC participant.

vanou commented 4 years ago

Yes. I’m not GSoC participant. Cheer up @Abhik1998 !

However, if and only if you don’t finish these issues in GSoC terms, I would like to work on this (if possible).

johnsonj commented 4 years ago

I adjusted the branding on this issue. This an open source project and our roadmap is open to all participants (GSoC or otherwise).

This particular issue we want to land before GSoC fully begins. This could help cluster-api migrate to the newest CoreDNS release without implementing a specific upgrade process.

vanou commented 4 years ago

I understand. I'll do my best. Thanks.

vanou commented 4 years ago

First, I'll tackle Provide metrics in the kubebuilder-declarative-pattern library .

vanou commented 4 years ago

Now I'm working on 2nd issue, and after I finish it, I would like to tackle 1st issue(Implement CoreDNS operator smoke test).

vanou commented 4 years ago

(Replying to this message on #36 )

Heyy @vanou, Care to release one issue?

Hi @SomtochiAma . Sorry for late reply.

I'm working on Provide metrics in the kubebuilder-declarative-pattern library. However my colleague @longkb working on #46 related to Integrate Kustomize with kubebuilder-declarative-pattern left company at end of this March and I was delegated access to this PR from him.

Now there is two options for us:

  1. As you are now working on,
  2. Another way is

Which one is better for you. And sorry for annoying you. If you reply to this, it is thankful for me.

vanou commented 4 years ago

Any way, currently I’m working on Provide metrics in the kubebuilder-declarative-pattern library, currently, I unassign me from #36.

Sorry.

somtochiama commented 4 years ago

@vanou Thank you for being considerate! I will pick up #36. Although, I will wait for the #50 to be merged before starting as it introduces significant file changes

vanou commented 4 years ago

@SomtochiAma OK. And sorry for I haven't unassigned me from #36 , now I have. Thank you.

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

neolit123 commented 4 years ago

/remove-lifecycle rotten

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

atoato88 commented 3 years ago

What's the current status of this, does anyone know that? Is it OK to close this issue?

Some issues related to this topic are described in top of this PR.

Mainly, related PRs are merged, but I'm not sure whether can I close or not.

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

k8s-ci-robot commented 3 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/cluster-addons/issues/47#issuecomment-781786171): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.