-
Notifications
You must be signed in to change notification settings - Fork 119
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
Deployment via Helm chart fail #76
Comments
I found something interesting. According to k8s docs:
If I try to change |
@paullaffitte : thanks for posting this issue. Please use the workaround mentioned in following issue:- |
Thanks, but unfortunately, it doesn't work either.
|
Please share the output of following command:-
|
EDIT: My bad, I was too fast and did a mistake, I wrote |
I know that 2 issues already exists about installing kube-fledged via YAML and operator fail but this one is about installing it with Helm, and it's not exactly the same problem.
When I run:
I got this error message:
The CertificateSigningRequest "kubefledged-webhook-server.kube-fledged" is invalid: spec.signerName: Invalid value: "kubernetes.io/legacy-unknown": the legacy signerName is not allowed via this API version
.My k8s version:
PS: FYI, if it can be useful:
EDIT:
If I try to edit the script and remove the
signerName
key, I got this quite interesting error message:error: error validating "STDIN": error validating data: ValidationError(CertificateSigningRequest.spec): missing required field "signerName" in io.k8s.api.certificates.v1.CertificateSigningRequestSpec; if you choose to ignore these errors, turn validation off with --validate=false
. Not sure if the issue is coming from kube-fledged or k8s itself 🤔The text was updated successfully, but these errors were encountered: