Skip to content
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

Create/Expose GKE loadbalancer IP (ingress controller support) via node template #37

Open
joshuap-cfy opened this issue Dec 1, 2017 · 0 comments

Comments

@joshuap-cfy
Copy link

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:

  • port: 80
    selector:
    app: hello-app
    tier: frontend
    type: LoadBalancer
    relationships:
  • type: cloudify.kubernetes.relationships.managed_by_master
    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant