Difference between revisions of "Kubectl apply -f ingress.yaml"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
== See also == | == See also == | ||
+ | * {{CRDS}} | ||
* {{kind: Ingress}} | * {{kind: Ingress}} | ||
* {{kubectl ingress}} | * {{kubectl ingress}} |
Revision as of 17:22, 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
See also
- Template:CRDS
kind: Ingress, nginx.ingress.kubernetes.io, networking.k8s.io/[v1Beta,v1 ], extensions/v1beta1, ingress.spec.rules, kubectl apply -f ingress.yaml, spec.tls, ingressClassName
kubectl 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: