Revisit Creating CustomResourceDefinitions from apiextensions-apiserver integration tests

[xmudrii]

Currently, the logic behind creating CustomResourceDefinitions in apiextensions-apiserver integration tests is ugly and could be improved. The CreateNewCustomResourceDefinition function creates CRD and then polls to make sure REST and cache storages are fully-initialized (there could be a race between initializing storages, check out this comment).

The polling is done by trying to perform each supported operation (list/watch/create/delete), and if there's no error, it's safe to say CRD is created and initialized.

As this is complicated, we want to try to replace it by utilizing EstablishingController, which is being implemented in #63068.

I would like to give a try on fixing this issue once #63068 is merged.

/kind feature
/sig api-machinery
/area custom-resources
/cc @sttts

[sttts]

/cc @nikhita @deads2k

@deads2k you remember this storage cache issue. Wouldn't it be good if we fix it on the server?

[lavalamp]

We need a general mechanism for apiservers (in HA) to coordinate on flipping the status to the correct state at the correct time, and not just for CRDs...

[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

[xmudrii]

/remove-lifecycle stale

[nikhita]

/remove-kind feature
/kind tech-debt

[nikhita]

/kind technical-debt

[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

[xmudrii]

/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

[xmudrii]

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