Difference between revisions of "ServiceName:"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
− | serviceName: k8s.io | + | |
+ | {{error validating ingress.yaml}} | ||
+ | |||
+ | serviceName: [[k8s.io]] | ||
== See also == | == See also == | ||
+ | * {{kind: Ingress}} | ||
* {{Ingress}} | * {{Ingress}} | ||
[[Category:Computing]] | [[Category:Computing]] |
Latest revision as of 18:19, 14 December 2023
error: error validating "ingress.yaml": error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "serviceName" in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "servicePort" in io.k8s.api.networking.v1.IngressBackend]; if you choose to ignore these errors, turn validation off with --validate=false error: error parsing ingress.yaml: error converting YAML to JSON: yaml: line 16: mapping values are not allowed in this context The Ingress "youingress" is invalid: spec.rules[0].http.paths[0].backend: Required value: port name or number is required Warning Rejected 31s nginx-ingress-controller spec.rules(0).host: Required value
serviceName: k8s.io
See also[edit]
kind: Ingress, nginx.ingress.kubernetes.io, networking.k8s.io/[v1Beta,v1 ], extensions/v1beta1, ingress.spec.rules, kubectl apply -f ingress.yaml, spec.tls, ingressClassName
- 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: