Lucas Servén Marín
Lucas Servén Marín
@bodgit yes please file as it’s own issue so we can track it. I’ll make sure the right people see it.
@bodgit thanks. @dmgaraway please let share your tfvars file. If you are also running on vmware, then we can close this issue in favor of #3080.
@dmgaraway Tectonic *does* have a VMware specific install, which is what @bodgit followed, though your approach should also work, however it is distinct. The bare metal install flow never expects...
@dmgaraway any update? Otherwise I'll close for now until we confirm you are still experiencing this issue.
Can you post the result of curling the OIDC configuration from a worker node? This URL should include the ingress domain i.e. it should be the same URL the console...
The reason kubectl complains with `kubectl error: error fetching provider config: invalid character '
@hapnermw if identity does die, then our goal would be to inspect the logs to see what caused the failure: `docker logs 4177e1e2ef52 > identity-logs.txt`. If the cluster fails the...
yeah, as this is currently written, it will always start and fail on non-leader-masters. we need to add another condition
@coresolve I checked the README and the repro case seems quite involved. Is the existing VPC required to hit this issue?
This is due to a mismatch between your version of Terraform and the intended version of Terraform for this release. The next release will solve this.