Difference between revisions of "Spec.IngressClassName"
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
== Related == | == Related == | ||
* [[Kubernetes: Ingress controllers]] | * [[Kubernetes: Ingress controllers]] | ||
+ | * [[kubectl describe ingressclass]] | ||
* [[kubectl get ingressclass]] | * [[kubectl get ingressclass]] | ||
Revision as of 16:42, 14 December 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
IngressClassName, kubectl get ingressclass, kubectl describe ingressclass, nginx.org/ingress-controller, ingress.k8s.aws/alb, Controller:
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
Advertising: