-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
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
Reconciler error on ipv6 cluster #462
Comments
Yes, the current behavior uses ipv4 to create mTLS certs. That's the main reason it's not working on your cluster. We'll definitely need an enhancement for ipv6. Thank you for reporting this @dcshiman! |
I have tried making the connection via ip here.
But it dsn't work cos the certificate is singed using |
Thank you for pointing this out @dcshiman |
reconcile is hanging early with a very not-useful error that "context deadline exceeded". I think I might be running into flux-iac/tofu-controller#462 I couldn't really get this controller to work a year ago, either. Looks like nothing has changed. Going to do a much simpler terraform setup with a sops-encrypted local state file checked into repo.
Partially solved by recent implementation to the pod resolution technique contributed to the project. Next step would be to deprecate the subport of ipv4 or ipv6 but use subdomain resolution as primary mechanism to talk to the runner. Would require a minimal code change. How to look up or connect. Create headless service for port subdomain resolution. Currently it's being created manually via Helm chart, which is suboptimal. |
If This value is |
Resolves #462 Signed-off-by: Balazs Nadasdi <balazs@weave.works>
Hi, I am having a similar issue as issues:365
Have tried setting the coreDNS with no luck, i am suspecting it's cos my cluster is on IPV6. Looking at the log, it looks like the tf controller is able to detect the status of runner pod, but can't figure out why its failing to run.
Here is the log form the controller,
What am i missing here ? Can direct me towards a solution ?
The text was updated successfully, but these errors were encountered: