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

Execute part of the provider Preflight Checks in the validation web-hook #699

Open
dmvolod opened this issue Jan 29, 2025 · 1 comment
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@dmvolod
Copy link
Member

dmvolod commented Jan 29, 2025

User Story
As operator, I want to know if something is wrong with the provider configuration as early as possible. It can be PreflightChecks phase do it< but it would be nice to know about potential errors synchronously while creating object.

Detailed Description
For this case, part of the PreflightChecks validations, except waiting for the CoreProvider to be ready could be integrated inside validation (create/update) web-hook logic. Its a best way for do it to fit with expectation described below.

Anything else you would like to add:
Nested from #693

[Miscellaneous information that will assist in solving the issue.]

/kind feature

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 29, 2025
@furkatgofurov7
Copy link
Member

/triage accepted

This makes sense to me

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 24, 2025
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. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants