You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run this command on GKE after doing a kubectl deployment, then a K8s load balancer is created and a public IP is exposed as well
$ kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
hello-app LoadBalancer 10.51.243.40 35.197.109.0 80:32459/TCP 1m
kubernetes ClusterIP 10.51.240.1 443/TCP 5d
I am looking to create a node template which exposes the external loadbalancer IP as well:
This node template above does not expose an external IP. It only creates an internal cluster IP. Do you know of an example or how to do this?
Not only does an external load balanced IP need to be created, but also ingress controller support so applications that run on the external load balanced IP are available.
The text was updated successfully, but these errors were encountered:
take a look at this kubectl command:
$ kubectl expose deployment hello-app --type=LoadBalancer --port 80 --target-port 8080
service "hello-app" exposed
If I run this command on GKE after doing a kubectl deployment, then a K8s load balancer is created and a public IP is exposed as well
$ kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
hello-app LoadBalancer 10.51.243.40 35.197.109.0 80:32459/TCP 1m
kubernetes ClusterIP 10.51.240.1 443/TCP 5d
I am looking to create a node template which exposes the external loadbalancer IP as well:
hello-app_svc:
type: cloudify.kubernetes.resources.Service
properties:
definition:
apiVersion: v1
kind: Service
metadata:
name: hello-app
labels:
app: hello-app
spec:
ports:
selector:
app: hello-app
tier: frontend
type: LoadBalancer
relationships:
target: kubernetes_master
This node template above does not expose an external IP. It only creates an internal cluster IP. Do you know of an example or how to do this?
Not only does an external load balanced IP need to be created, but also ingress controller support so applications that run on the external load balanced IP are available.
The text was updated successfully, but these errors were encountered: