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

Is there a way to create global LB with kubernetes ingress? #5240

Closed
qkos opened this issue Jun 24, 2016 · 6 comments
Closed

Is there a way to create global LB with kubernetes ingress? #5240

qkos opened this issue Jun 24, 2016 · 6 comments
Assignees
Labels
area/kubernetes kind/enhancement Issues that improve or augment existing functionality
Milestone

Comments

@qkos
Copy link

qkos commented Jun 24, 2016

At the moment you can scale the LB for kubernetes ingress via the scale annotation. I have a use case where I am using an autoscaling group for my kubernetes environment and I have an ELB attached to it. The UI allows creating LB with global scale that spins up a container on each host.

It seems like currently the ingress-controller does not support this.

At the moment I am using the ingress-controller independently on the stable rancher build. Any chance this can be included in 1.1.0?

@alena1108 would you be able to comment on this perhaps?

@deniseschannon
Copy link

@mechatama We have already released 1.1, but I've changed this as an enhancement request. If others are interested in this concept, we can look into prioritizing it.

@deniseschannon deniseschannon added kind/enhancement Issues that improve or augment existing functionality area/balancer area/kubernetes labels Jul 2, 2016
@will-chan will-chan modified the milestone: Unscheduled Oct 8, 2016
@LoicMahieu
Copy link

@deniseschannon I think some people, including me, is really interested on more control of the `ingress-controller.
See:

@0megam
Copy link

0megam commented Dec 16, 2016

+1

@ghost
Copy link

ghost commented Jan 3, 2017

👍

@wlan0
Copy link

wlan0 commented Jan 17, 2017

This feature has been added since v1.4.0-rancher release of kubernetes

Ensure that you have more than one host added to rancher

Steps to test:

  1. create the reference RC and Service shown below.
apiVersion: v1
kind: Service
metadata:
  name: nginx-service
  labels:
    k8s-app: nginx-service
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
    name: http
  selector:
    k8s-app: nginx-service
---
apiVersion: v1
kind: ReplicationController
metadata:
  name: nginx-service
spec:
  replicas: 1
  selector:
    k8s-app: nginx-service
  template:
    metadata:
      labels:
        k8s-app: nginx-service
    spec:
      terminationGracePeriodSeconds: 60
      containers:
      - name: nginx-service
        image: nginx:latest
        ports:
        - containerPort: 80
  1. Using this reference ingress definition, create the ingress controller:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test
  annotations:
    config: "defaults\n balance source\nglobal\nmaxconnrate 60"
    io.rancher.scheduler.global: "true"
spec:
  backend:
    serviceName: nginx-service
    servicePort: 80

This will create the lb service globally. Check that the lb-service container gets launched on every host by checking the host view in rancher UI.

@soumyalj
Copy link

Tested with rancher v1.4.0-rc2 and K8s 1.5.2-rancher1. Global Kubernetes Ingress LB is functional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubernetes kind/enhancement Issues that improve or augment existing functionality
Projects
None yet
Development

No branches or pull requests

8 participants