Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

KUDO should wait for cluster-scoped resources (e.b. CRDs) to become available in the cluster #1341

Closed
zen-dog opened this issue Feb 12, 2020 · 1 comment
Closed

KUDO should wait for cluster-scoped resources (e.b. CRDs) to become available in the cluster #1341

zen-dog opened this issue Feb 12, 2020 · 1 comment
Assignees
@alenkacz
Labels
kind/enhancement

Comments

@zen-dog
Copy link
Contributor

zen-dog commented Feb 12, 2020

What would you like to be added:
KUDO manager currently assumes that cluster-scoped resources are immediately healthy and moves on with the execution of the next plan step. However, it takes time for cluster-scoped resources to appear visible in the cluster, that's why e..g controller-runtime implements busy-waiting when applying CRDs. KUDO manager needs similar logic (and we already propagate the discovery client to the tasks)
@ANeumann82 ANeumann82 mentioned this issue Aug 19, 2020
Merged
@alenkacz alenkacz self-assigned this Aug 21, 2020
@ANeumann82
Copy link
Member

This was fixed in #1648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alenkacz alenkacz

Labels
kind/enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alenkacz @ANeumann82 @zen-dog