-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Cluster should be has external ip of public load balancer ? #23
Comments
@lucacalcaterra this is the output of what? kubectl get nodes -o wide? For the services exposed by k3s, k3s uses a different kind of approach unlike k8s. You can find more info here in Service Load Balancer chapter. And If you want to integrate k3s service with OCI LoadBalancer you have to install OCI CCM. With OCI CCM installed if you expose a service with a LoadBalancer service, then you get a public ip address for your service (the OCI CCM will create a Load Balacner for you). The OCI CCM integration is a work in progress task, see PR #16 |
@garutilorenzo this is the output of kubectl get svc -A So probably nothing wrong with this repo and i should use the OCI CCM as you suggest. Thanks ! |
anyway, i think you should see load balancer's public ip as external addres and not the backends ip's |
Dear @lucacalcaterra, the answer is no, with this module you can't see LP public IPs (not at the moment). This module install k3s like it was an on-prem installation, with "no CCM support" so you can't see LB public IPs.
you can't see this public IP with kubectl, since there is no CCM installed. I hope is more clear now. |
Meanwhile your reply... i'll understand it... So your reply clarify all the things. thanks ! |
@garutilorenzo services exposed with load balancer see private ip's and not external ip (public load balancer). I suppose k3s should be initialized with node-external-ip and so on...
I'm wrong ?
The text was updated successfully, but these errors were encountered: