-
Notifications
You must be signed in to change notification settings - Fork 9
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
support for kubernets 1.20 #23
Comments
I unfortunately haven't tested this with 1.20 yet. These log entries aren't necessarily a sign of problem though. Do you have any other issues, or a more complete log? |
i get no other logs, iv been looking thru the code, and im not seeing any of the log lines i would expect, it literary prints only those lines. so something changed somewhere and its not getting events or so, and no normal execution paths happen that trigger logging. what are your suggestions? |
So theres is some operator error involved, i cant tell where, i had not requested debug logs, here they are after changing configs:
im unsure what is going on. |
This portion:
Does it mean its the interaction with metallb thats problematic? it seems to see that any of my IP's are attached. |
Yes, this looks like it could be a metallb issue. What does And what version of hcloud-ip-floater are you using? |
I think i have it resolved, its like most issues, operator error, i mixed up my service "selector", (reversed some hyphenated words). so false alarm. without the selectors, this tool could not see live pods for the service, so it would not attach the ips. its easily confused to be a metallb issue, but its not. |
Im unable to get this to work on kubernetes 1.20, its unable to assign the ip's. is support for this coming in future?
here is the current error:
The text was updated successfully, but these errors were encountered: