-
Notifications
You must be signed in to change notification settings - Fork 17
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
[BUG] Generated svc seems to be invalid when using namespaced and manually making secret #35
Comments
Oh, there is no validating webhook to make sure it's right? |
Hi @samip5, thanks for opening the issue; gonna investigate. The secret and service you're using are in the same namespace? ( |
The generated svc and secret are in the same namespace, but my goal is that the backend for the onionservice is not in the same namespace (which doesn't seem supported)... |
Still not sure what's going on; from the log it seems the controller is not able to build the
Can you test deploying the example: And check if the error is reproduced? Also, what k8s version is your affected cluster using? |
I think it would be useful to include a validating webhook so that there is no such wierd errors when the manifest is incorrect. I believe it was the result of not including rules at all eg https://github.com/samip5/k8s-cluster/blob/987bb26aedbbbe7672c80cce0e06f0297a5d5179/cluster/apps/tor/services/ahmia-hidden.yaml (which used api version |
Thanks @samip5. I agree, a webhook to validate those will help. I'll change this one too enhancement and will start working on it. |
@bugfest Was this forgotten? |
Hi @samip5, not forgotten but deprioritized; I've been working on other bug fixes and OLM future migration. I'll keep this open so I don't forget about it. Any implementation draft will welcomed via PR. Thanks for your understanding |
Describe the bug
When trying to deploy a onionService, it fails with spec.ports being invalid on the resulting svc but I did not set those.
To Reproduce
Expected behavior
I would have expected it to work out of the box.
Additional information
System (please complete the following information):
Additional context
Values are here
The text was updated successfully, but these errors were encountered: