Difference between revisions of "Spec.IngressClassName"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
− | + | == Single rule == | |
spec: | spec: | ||
ingressClassName: nginx | ingressClassName: nginx |
Revision as of 16:41, 30 November 2023
Single rule
spec: ingressClassName: nginx rules: - host: yourhost.com http: paths: - path: / pathType: Prefix backend: service: name: yourservicename port: number: 80
Multiple rules
spec: ingressClassName: nginx rules: - host: chart-example.local http: paths: - path: / pathType: Prefix backend: service: name: grafana port: number: 80 - host: prometheus.chart-example.local http: paths: - path: / pathType: Prefix backend: service: name: prometheus-server 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: