ingress-nginx
ingress-nginx copied to clipboard
request block1 offset 512 doesn't match the current position 0
What happened:
What you expected to happen: kubectl edit cm -n ingress-nginx udp-services
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use kubectl version
):
Environment:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
-
Kernel (e.g.
uname -a
):
-
Install tools:
-
Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
-
-
Basic cluster related info:
-
kubectl version
-
kubectl get nodes -o wide
-
-
How was the ingress-nginx-controller installed:
- If helm was used then please show output of
helm ls -A | grep -i ingress
- If helm was used then please show output of
helm -n <ingresscontrollernamespace> get values <helmreleasename>
- If helm was not used, then copy/paste the complete precise command used to install the controller, along with the flags and options used
- if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances
- If helm was used then please show output of
-
Current State of the controller:
-
kubectl describe ingressclasses
-
kubectl -n <ingresscontrollernamespace> get all -A -o wide
-
kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
-
kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>
-
-
Current state of ingress object, if applicable:
-
kubectl -n <appnamespace> get all,ing -o wide
-
kubectl -n <appnamespace> describe ing <ingressname>
- If applicable, then, your complete and exact curl/grpcurl command (redacted if required) and the reponse to the curl/grpcurl command with the -v flag
-
-
Others:
- Any other related information like ;
- copy/paste of the snippet (if applicable)
-
kubectl describe ...
of any custom configmap(s) created and in use - Any other related information that may help
- Any other related information like ;
How to reproduce this issue:
Anything else we need to know: