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.

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

Add validation to config.waitForPodsReady #3809

Open
3 tasks
PBundyra opened this issue Dec 11, 2024 · 5 comments
Open
3 tasks

Add validation to config.waitForPodsReady #3809

PBundyra opened this issue Dec 11, 2024 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@PBundyra
Copy link
Contributor

What would you like to be added:
Add validation for WaitForPodsReady that asserts timeout, blockAdmission and requeuingStrategy are defined only if enable is set to True

Why is this needed:

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

@PBundyra PBundyra added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 11, 2024
@mimowo
Copy link
Contributor

mimowo commented Dec 11, 2024

Hm, not sure about that. What about the use case that an admin has the feature configured and just wants to disable it temporarily and reenable quickly with the same config.

@tenzen-y
Copy link
Member

We already checked the waitForPodsReady only when the waitForPodsReady is enabled here:

if !WaitForPodsReadyIsEnabled(c) {
return allErrs
}

So, I was not sure this validation motivation.

@PBundyra
Copy link
Contributor Author

Do we give any feedback to a user in case they configured the rest of the fields, but forgot to switch the enable field?

@mimowo
Copy link
Contributor

mimowo commented Dec 11, 2024

I don't think we do, maybe we could leave some useful log or use a warning.

@tenzen-y
Copy link
Member

maybe we could leave some useful log or use a warning.

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants