I think elasticsearch service doesn't need an LB. Only Kibana (because its a UI). The other services are ClusterIP by default because they are not specified in the code (better to actually type it in). ClusterIP is fine because they need to communicate in the cluster but don't need to be accessed from outside. I would look for some official yamls to use for your projects.
I got a crashbackloop error for the elastic search pod and for kibana the error I have is "page isn't working" the loadbalancer dns name did not send any data
Thank you for watching my videos. Please check the resource (CPU/Memory) of your EC2 instance and allocate resources accordingly at repsctive Containers
Very nice, you explained it well.
Thank you for watching my videos.
Glad that it helped you.
Why do we need two loadbalancer? Can't we use one? I mean path based routing to services using single alb?
Thank you for watching my videos Indeed we can use , best suggestions would be to use an independent load balancer.
I think elasticsearch service doesn't need an LB. Only Kibana (because its a UI).
The other services are ClusterIP by default because they are not specified in the code (better to actually type it in). ClusterIP is fine because they need to communicate in the cluster but don't need to be accessed from outside.
I would look for some official yamls to use for your projects.
I got a crashbackloop error for the elastic search pod and for kibana the error I have is "page isn't working" the loadbalancer dns name did not send any data
Thank you for watching my videos.
Please check the resource (CPU/Memory) of your EC2 instance and allocate resources accordingly at repsctive Containers
@@cloudquicklabs Thank you
wow
Thank you for watching my videos.
Glad that it helped you.