Difference between revisions of "Kubectl apply -f ingress.yaml"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
[[error: resource mapping not found]] for name: "your-ingress" namespace: "your-namespace" from "ingress.yaml": no matches for kind "[[Ingress]]" in version "[[networking.k8s.io/v1beta1]]" [[ensure CRDs are installed first]] | [[error: resource mapping not found]] for name: "your-ingress" namespace: "your-namespace" from "ingress.yaml": no matches for kind "[[Ingress]]" in version "[[networking.k8s.io/v1beta1]]" [[ensure CRDs are installed first]] | ||
| − | + | ||
Solution: change [[networking.k8s.io/v1beta1]] for [[networking.k8s.io/v1]] or your K8s version: kubectl api-resources | grep [[networking.k8s.io]] | Solution: change [[networking.k8s.io/v1beta1]] for [[networking.k8s.io/v1]] or your K8s version: kubectl api-resources | grep [[networking.k8s.io]] | ||
Revision as of 17:54, 14 December 2023
error: resource mapping not found for name: "your-ingress" namespace: "your-namespace" from "ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1" ensure CRDs are installed first Solution: change networking.k8s.io/v1beta1 for networking.k8s.io/v1 or your K8s version: kubectl api-resources | grep networking.k8s.io
See also
- CRD,
kind: CustomResourceDefinition kind: Ingress, nginx.ingress.kubernetes.io, networking.k8s.io/[v1Beta,v1 ], extensions/v1beta1, ingress.spec.rules, kubectl apply -f ingress.yaml, spec.tls, ingressClassNamekubectl create ingress | kubectl get ingress,kubectl describe ingress, Kong, Kubernetes Gateway API, kubectl apply -f ingress.yaml- Ingress controllers, NGINX Ingress Controller,
minikube addons enable ingress,kubectl get ingress, kubectl get ingressclass, kubectl describe ingress,Ingress:, Ingress API, AWS Load Balancer Controller, Envoy Proxy, GKE Ingress, Kubernetes Gateway API,ingress.k8s.aws, ingresses.networking.k8s.io,kind: Ingress: (tls:, hosts:),SuccessfullyReconciled
Advertising:
