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

Trying to validate Native 'tweaked' install on Rancher Desktop K8s (v1.29.5stable) on Mac M1: functions deploy fails #2375

Open
stevef1uk opened this issue Jun 19, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@stevef1uk
Copy link

stevef1uk commented Jun 19, 2024

I have manually deployed Istio & Native on my local cluster as the automated script did not work. All pods seem to be running & I was able to deploy ok a sample istio application.

I had to manually edit some Knative yaml files to change V1beta1 to v1alpha1 to get the yaml files (serving-core.yam & serving-crds.yaml) to deploy successfully so I am not sure of the state our my installation. I am actually trying to test Kserve which requires the above.

I have used the func command to create a go example and built it locally ok. When I try to deploy I am getting the following errors:

Error: deploy error. knative deployer failed to deploy the Knative Service: admission webhook "validation.webhook.serving.knative.dev" denied the request: validation failed: must not set the field(s): spec.template.spec.containers[0].securityContext.allowPrivilegeEscalation, spec.template.spec.containers[0].securityContext.seccompProfile

I tried Googling and couldn't find anything on this issue. I adding the work arounds I used to use on Openshift without success:

oc adm policy add-scc-to-user anyuid -z default -n  knative-serving 
oc adm policy add-scc-to-user anyuid -z default -n kserve-test 

Any thoughts would be appreciated.

Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant