-
Notifications
You must be signed in to change notification settings - Fork 19
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
Feature: Validation webhook for serviceexport #358
Comments
would like to work on this ,can you please assign me this issue? @mridulgain |
sure @kon3m. I have assigned this issue to you. Let us know @kon3m, if you need any help with this issue or you can connect directly with @mridulgain for any discussion on slack channel. |
@narmidm @mridulgain i cannot work on this issue until this PR gets merged. Will work on another issue till then. |
Certainly, @kon3m, I will attempt to close the other pull request soon. After that, you can return to this issue. |
Hey @kon3m are you currently working on this issue ? |
🔖 Feature description
Validate serviceexport objects during admission.
🎤 Pitch
Exporting a service by creating a
serviceexport
object only makes sense when it's created withing the application namespace of the specified slice. Currently user may create aserviceexport
with a slice name even if the slice object is not present on that cluster or in case it's present but doesn't even has any application namespace onboarded.✌️ Solution
Implement a validation webhook that checks,
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: