Difference between revisions of "Spec.IngressClassName"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | |||
| + | spec: | ||
| + | ingressClassName: nginx | ||
| + | rules: | ||
| + | - host: yourhost.com | ||
| + | http: | ||
| + | paths: | ||
| + | - path: / | ||
| + | pathType: Prefix | ||
| + | backend: | ||
| + | service: | ||
| + | name: tool-nginx-ap | ||
| + | port: | ||
| + | number: 80 | ||
== Changes == | == Changes == | ||
Revision as of 11:06, 12 September 2023
spec:
ingressClassName: nginx
rules:
- host: yourhost.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: tool-nginx-ap
port:
number: 80
Changes
- Ingresses can specify the class they are associated with by using a new ingressClassName field on Ingresses
Related
See also
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 - Kubernetes controllers: Ingress,
controller., AWS Load Balancer controller, kubectl describe ingressclass nginx - Kubernetes networking: network policies, Network Policy Providers, CNI, Calico, flannel, Service mesh, Istio,
kube-proxy, coredns, AWS VPC CNI: vpc-cni, Kubernetes: Ingress controllers, IPVS, ServiceTypes:LoadBalancer, ClusterIP, NodePort, ExternalName, Endpoints, EndpointSlices, Kubernetes DNS,svc.cluster.local, Weave Net
Advertising:
