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

Installation error: no matches for kind "ClusterRbacConfig" in version "rbac.istio.io/v1alpha1" #5391

Closed
fuhuifang opened this issue Nov 10, 2020 · 5 comments
Labels

Comments

@fuhuifang
Copy link

/kind bug

What steps did you take and what happened:
Hello! I was following the instructions here. When I ran kfctl apply -V -f ${CONFIG_URI}, I got the following error:
WARN[0063] Encountered error applying application istio: (kubeflow.error): Code 500 with message: Apply.Run : unable to recognize "/tmp/kout474140078": no matches for kind "ClusterRbacConfig" in version "rbac.istio.io/v1alpha1" filename="kustomize/kustomize.go:266"

and it just keeps retrying. Do you know how to fix this? Thanks!

Environment:

  • Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard):
  • kfctl version: kfctl v1.1.0-0-g9a3621e
  • Kubernetes platform: (e.g. minikube): Azure Kubernetes Service
  • Kubernetes version: Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.13", GitCommit:"30d651da517185653e34e7ab99a792be6a3d9495", GitTreeState:"clean", BuildDate:"2020-10-20T16:22:33Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
  • OS (e.g. from /etc/os-release): ubuntu 16.04.7 LTS
@torbre16
Copy link

Hi.

I ran into the same issue today. I first tried to install Kubeflow with Istio 1.7.4, which resulted in the same error described by you.

After a downgrade to Istio 1.6.13 I was able to complete the installation. The CONFIG_URI used in the instructions mentioned by you points to https://raw.githubusercontent.com/kubeflow/manifests/v1.1-branch/kfdef/kfctl_azure.v1.1.0.yaml, which contains the following comment:

"It is expected to have Istio 1.6.x installed in istio-system namespace"

Maybe that also helps you to perform the installation? It seems that further adjustments are needed to make it compatible with Istio 1.7.x.

Best regards,
Torbre16

@fuhuifang
Copy link
Author

@torbre16

Hi.

I ran into the same issue today. I first tried to install Kubeflow with Istio 1.7.4, which resulted in the same error described by you.

After a downgrade to Istio 1.6.13 I was able to complete the installation. The CONFIG_URI used in the instructions mentioned by you points to https://raw.githubusercontent.com/kubeflow/manifests/v1.1-branch/kfdef/kfctl_azure.v1.1.0.yaml, which contains the following comment:

"It is expected to have Istio 1.6.x installed in istio-system namespace"

Maybe that also helps you to perform the installation? It seems that further adjustments are needed to make it compatible with Istio 1.7.x.

Best regards,
Torbre16

Thanks @torbre16 ! It did fix the issue.

Needs Triage automation moved this from To Do to Closed Nov 10, 2020
@kubeflow-bot kubeflow-bot removed this from Closed in Needs Triage Nov 10, 2020
@DavidGeW
Copy link

I took the same steps as you did, and in addition to this problem, I encountered another problem.Have you ever encountered the following problem?Thanks.

kfctl exited with error: failed to apply: (kubeflow.error): Code 500 with message: kfApp Apply failed for kustomize: (kubeflow.error): Code 500 with message: Apply.Run : error when creating "/tmp/kout125728891": admission webhook "validation.istio.io" denied the request: configuration is invalid: TLS match must have at least one SNI host.

@berndverst
Copy link
Member

@DavidGeW that sounds like a separate issue with cert-manager instead. If you still have that problem, can you file a separate issue please? I recently saw another such issue.

@DavidGeW
Copy link

DavidGeW commented Dec 4, 2020

@DavidGeW that sounds like a separate issue with cert-manager instead. If you still have that problem, can you file a separate issue please? I recently saw another such issue.

@berndverst Thanks! I've solved this problem with #5070, it's a problem caused by the upgrade of istio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants