We’ve got a Rancher-Server running at AWS, we’ve created a k8s env and i’ve created a demo deployment and service running nginx.
Service is type “loadbalancer”
(we’re running in a VPC in a private subnet)
I see the deployment and service all successfully created - but the loadbalancer ingress is a private IP.
“status”: {
“loadBalancer”: {
“ingress”: [
{
“ip”: “PRIVATE IP”
}
And I do not see any LB created at AWS.
So to sum up; Deployment and service created successfully through k8s.
Loadbalancer not being created at AWS.
Our r-hosts have elb-full-access roles attached (and our r-server does as well, since I have been trying to troubleshoot this)
Any help?
I’m under the impression that by declaring “type: loadbalancer” for my service, there should be a LB created at AWS. Is that correct?