Difference between revisions of "Kubectl describe ingress"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lowercase}} | {{lowercase}} | ||
| + | |||
| + | == Related == | ||
| + | * <code>[[kubectl get ingress]]</code> | ||
== See also == | == See also == | ||
* {{kubectl ingress}} | * {{kubectl ingress}} | ||
* {{kubectl get}} | * {{kubectl get}} | ||
| − | |||
* {{Ingress}} | * {{Ingress}} | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Revision as of 12:23, 25 May 2022
Related
See also
kubectl create ingress | kubectl get ingress,kubectl describe ingress, Kong, Kubernetes Gateway API, kubectl apply -f ingress.yamlkubectl get: [all|componentstatus | pods | apiservices | events|event|nodes|replicaset|services|svc|namespaces|hpa|secret | deployments | serviceaccounts | endpoints | daemonset | networkpolicy],kubectl get -h- 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:)
Advertising:
