[tracking bug] CoreDNS Operator about cluster-addons HOT 23 CLOSED

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.

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

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?

from cluster-addons.

@vanou I will be working upon them.

from cluster-addons.

@Abhik1998 I understand. Sorry for worrying.

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

(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,
   • you take assignee of kustomize integration issue and work on it
   • and I give up #46 (because this issue is closely related to kustomize integration issue)
     (or can I work on #46 after you finish kustomize integration issue?)
   • and I concentrate on Provide metrics in the kubebuilder-declarative-pattern library & Implement CoreDNS operator smoke test (or one of it) which I currently have assignee.
2. Another way is
   • I un-assign me from Provide metrics in the kubebuilder-declarative-pattern library & Implement CoreDNS operator smoke test
   • and you take assignee of above two
   • then l work on #46 & kustomize integration issue

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

from cluster-addons.

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

Sorry.

from cluster-addons.

@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

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

from cluster-addons.

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

from cluster-addons.

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.

• #36 : closed by fejta-bot, current status is unknown..
• kubernetes-sigs/kubebuilder-declarative-pattern/issues/65 : closed
• kubernetes-sigs/kubebuilder-declarative-pattern/issues/56 : closed by fejta-bot, but some PRs related to this are merged.
• #27 : closed

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

from cluster-addons.

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

from cluster-addons.

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

from cluster-addons.

@fejta-bot: Closing this issue.

from cluster-addons.