-
Notifications
You must be signed in to change notification settings - Fork 91
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
NFT: Add NodePort Support to KPNG #15
Comments
coredns logs:
Collected by turning:
|
as a smoke test, heres what it sais when i curl
Thus, the |
im starting to wonder: is it possible that loopback services dont work ( or do work ) for example , coredns seems to work 50% of the time , when im using calico as the CNI. maybe thats because calico as CNI allowed multinode networking to be working.... Im goint to try an experiment of increasing the node count.... |
thanks for testing, yeah NodePorts, I've not implemented that yet, but it shouldn't be too hard |
ahhhh yes ok that explains it :) |
Ok, the remaining tests:
|
ill separate that into separate issues. |
Looks like NodePorts arent working....
is this NFT specific?
@andrewsykim was asking wether or not the nodeport issue was provider specific, i think it is...
because we have nodeports in the spec
DETAILS
Ive finished running the conformance results for the hack/ scripts:
The major hole at the moment is ~ nodeport support
It appears that most of the service dependent tests fail.
The results are:
The text was updated successfully, but these errors were encountered: