CoreDNS Operator: Smoke Tests

[johnsonj]

Create an end-to-end smoketest for coredns-operator. The test should run locally by default (via kind or kinder) and support running on a remote kubernetes cluster when provided.

The test should implement and validate the following scenarios:

• Creation 
• Deletion
• Configuration Change
• Upgrade the version of CoreDNS
• Downgrade the version of CoreDNS

This work will require adding multiple versions to the CoreDNS version directory.

Implementation Nodes:

• The test can be based off the existing dashboard-operator smoketest [src].
• If there is bandwidth, write a test framework in kubebuilder-declarative-pattern and consume it in the coredns-operator repo. 
  • Roughly: A test framework would perform the execution of the test (eg, install the operator, CRDs), provide a set of common validation functions (eg verifyNoWorkloadsWithLabel) and allow the operator author to pass in their own “AddonTest” object.
  • The kubebuilder/controller-runtime folks may be providing something like this (/cc @ecordell)

/cc @annp1987

[fejta-bot]

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

[johnsonj]

/remove-lifecycle stale

…

On Sun, Mar 1, 2020 at 3:02 PM fejta-bot ***@***.***> wrote: 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 <https://github.com/fejta>. /lifecycle stale — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#36?email_source=notifications&email_token=AADGRZMESE22UB32WFZNXILRFLSPVA5CNFSM4JULUOZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNOKTQ#issuecomment-593159502>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADGRZLQSSCRVGU46LRTEUTRFLSPVANCNFSM4JULUOZQ> .

[vanou]

After I finish this issue, I'll tackle this.

/assign

[somtochiama]

Heyy @vanou, Care to release one issue?

[vanou]

Sorry. Currently I’m working on #65. So, currently, I unassign me from this.

/unassign

[somtochiama]

/assign

@johnsonj I wanted to start working on the test framework first in kubebuilder-pattern, wdyt?

[johnsonj]

SGTM @somtochiama !

[fejta-bot]

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

[vanou]

/remove-lifecycle stale

[fejta-bot]

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]

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]

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-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

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-testing, kubernetes/test-infra and/or fejta.
/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.