You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
* Error: Provider produced inconsistent final plan
...
kubernetes-alpha" produced an invalid new value for
.object.spec.selector.matchLabels.controller-uid
.object.spec.template.metadata.labels.controller-uid
...
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
...
* spec.ports[0].nodePort: Invalid value: 32769: provided port is not in the valid range.
Port behavior might be fixed else where to the k8s API.
Second terraform apply
After the first TF apply an ingress-nginx-controller pod was left in ContainerCreating state.
By retrying terraform apply a "TERRAFORM CRASH" raises due to the running ContainerCreating
pod in the ingress-nginx ns. Deleting pod or TF destroy was required before applying again.
Is that CRASH behavior expected
and why does that error "Provider produced inconsistent final plan" occur ?
I would appreciate it very much
if you could help me get that nginx-controller running the kubernetes-alpha way.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Apr 8, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
using the ingress-nginx controller repo throws different errors in the apply process.
Used Versions
kubectl version --short=true
Steps to Reproduce (1) - create main.tf from Source
Steps to Reproduce (2) - run terraform
main.tf
ingress-nginx-controller manifest
log snippet's
cat ingress-nginx-trace.log | egrep -B20 -A5 -i "inconsist|failed"
ingress-nginx-trace.log
Issues
Port behavior might be fixed else where to the k8s API.
Second terraform apply
After the first TF apply an ingress-nginx-controller pod was left in ContainerCreating state.
By retrying terraform apply a "TERRAFORM CRASH" raises due to the running ContainerCreating
pod in the ingress-nginx ns. Deleting pod or TF destroy was required before applying again.
Is that CRASH behavior expected
and why does that error "Provider produced inconsistent final plan" occur ?
I would appreciate it very much
if you could help me get that nginx-controller running the kubernetes-alpha way.
The text was updated successfully, but these errors were encountered: