We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have an invalid ingress that I tried to deploy. It reported success but the ingress did not change or show me the error.
Error should have been: error: ingresses "web" could not be patched: cannot convert int64 to string
error: ingresses "web" could not be patched: cannot convert int64 to string
What I saw:
[INFO][2017-09-08 19:28:45 +0000] Deploying resources: [INFO][2017-09-08 19:28:45 +0000] - Ingress/web (timeout: 30s) Successfully deployed in 8.8s: Ingress/web
The text was updated successfully, but these errors were encountered:
That's very odd. Do you have the relevant part of the old/new specs I could use to try to reproduce this?
Sorry, something went wrong.
here's a sample:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: web annotations: kubernetes.io/ingress.class: nginx ingress.kubernetes.io/limit-rps: 30 labels: name: web app: foobar environment: production spec: rules: - host: foobar.example.com http: paths: - backend: serviceName: web servicePort: 80
Notice the ingress.kubernetes.io/limit-rps is an int where it should be a string. This deploy was going from no annotation to adding this annotation.
ingress.kubernetes.io/limit-rps
Stale, this is likely issue with kubectl itself given the issue was with the resource patching.
Breadcrumb: this is the upstream bug: kubernetes/kubernetes#59113
No branches or pull requests
I have an invalid ingress that I tried to deploy. It reported success but the ingress did not change or show me the error.
Error should have been:
error: ingresses "web" could not be patched: cannot convert int64 to string
What I saw:
The text was updated successfully, but these errors were encountered: