voyagermesh / voyager Goto Github PK

View Code? Open in Web Editor NEW

1.3K 35.0 141.0 6.05 MB

🚀 Secure L7/L4 (HAProxy) Ingress Controller for Kubernetes

Home Page: https://voyagermesh.com

License: Apache License 2.0

Shell 100.00%

kubernetes haproxy tls ingress appscode voyager

voyager's Introduction

Voyager

Secure L7/L4 Ingress Controller for Kubernetes

PSA: As previously announced, we have removed the deprecated Voyager v11.x and v12.x images. Please update to the latest v2022.01.10 release!

Voyager is a HAProxy backed secure L7 and L4 ingress controller for Kubernetes developed by AppsCode. This can be used with any Kubernetes cloud providers including aws, gce, gke, azure, acs. This can also be used with bare metal Kubernetes clusters.

Ingress

Voyager provides L7 and L4 load balancing using a custom Kubernetes Ingress resource. This is built on top of the HAProxy to support high availability, sticky sessions, name and path-based virtual hosting. This also supports configurable application ports with all the options available in a standard Kubernetes Ingress.

Certificate

Voyager can automatically provision and refresh SSL certificates (including wildcard certificates) issued from Let's Encrypt using cert-manager.

Installation

To install Voyager, please follow the guide here.

Using Voyager

Want to learn how to use Voyager? Please start here.

Contribution guidelines

Want to help improve Voyager? Please start here.

Acknowledgement

docker-library/haproxy https://github.com/docker-library/haproxy
kubernetes/contrib https://github.com/kubernetes/contrib/tree/master/service-loadbalancer
kubernetes/ingress https://github.com/kubernetes/ingress
xenolf/lego https://github.com/appscode/lego
kelseyhightower/kube-cert-manager https://github.com/kelseyhightower/kube-cert-manager
PalmStoneGames/kube-cert-manager https://github.com/PalmStoneGames/kube-cert-manager
Kubernetes cloudprovider implementation
openshift/generic-admission-server https://github.com/openshift/generic-admission-server
TimWolla/haproxy-auth-request https://github.com/TimWolla/haproxy-auth-request

Support

We use Slack for public discussions. To chit chat with us or the rest of the community, join us in the AppsCode Slack team channel #general. To sign up, use our Slack inviter.

If you have found a bug with Voyager or want to request for new features, please file an issue.

voyager's People

Contributors

Stargazers

Watchers

Forkers

jakeaustwick euank mikalv arehmandev rimusz-lab zoues shamash2014 aland-zhang julianvmodesto lemaral codefreshdemo thecodeassassin onzo-com aimof johnswan jipperinbham nstott markjacksonfishing cp-richard rstuven zrbilvoe rschoultz-wl johnjjung pierreozoux leprechaun zhuomingliang wtdragon xcompass terrycorley nhumrich drf kresodenis isman-usoh sajibcse68 raditsp itc3-devops tekacs rigdon samiracho tahsinrahman bewiwi hofmeister steveum0105 joshuacox lukw00heck schubter cober zhuvikin jaymeyerowitz lrodorigo mathewusher zsandrus renesugar ocdi conorbranagan patgpraj mwx23 curx awesomegolang kidmam bodewig packetgg datadog sammy bpineau easonwang01 scofields endrec vipulsankhe10 thomaskliszowski elynnyap alekseypon w23123 m4rcu5 dantgardner iammaze whitemike889 wanghe-fit2cloud fleximux ssro isgasho binnyrs researchmore zhashuyu l10xbin sniip-code sadlil mildred nimazahedi jasi110 kirrmann weeband lightistor cbepx soosap ibuystuff clenimar fabiofi bg-master zeromsi

voyager's Issues

Service ports should be int

cloud-provider & cloud-name can't be always required

https://github.com/appscode/voyager/blob/master/cmd/voyager/main.go#L31

This is a problem is user is using baremetal provider.

Use service account with reduced permission to run operator

https://coreos.com/operators/prometheus/docs/latest/user-guides/getting-started.html

Updating Ingress annotations are not picked up by controller

Currently, when I add or update annotations to my Ingress object, none of the changes are made.

For example, before:

apiVersion: appscode.com/v1beta1
kind: Ingress
metadata:
  name: frontend
  labels:
    app: frontend
spec:
  # Default backend
  backend:
    serviceName: echoserver
    servicePort: 80

After:

apiVersion: appscode.com/v1beta1
kind: Ingress
metadata:
  name: frontend
  labels:
    app: frontend
  annotations:
    # Enable the AWS Proxy Protocol
    # NOTE(jmodes): We need to have `bind :80 accept-proxy` for HAProxy to accept Proxy Protocol requests.
    # ingress.appscode.com/annotations.service: '{"service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*"}'
    # Number of HAProxy replicas to run
    ingress.appscode.com/replicas: 1
    # Open HAProxy stats on port 1936
    ingress.appscode.com/stats: true
    ingress.appscode.com/stats.secretName: frontend-stats
spec:
  # Default backend
  backend:
    serviceName: echoserver
    servicePort: 80

After applying the new Ingress, none of the changes were enacted by the controller.

Use HAProxy 1.7.5

Need to update the default setup
https://github.com/appscode/voyager/search?utf8=%E2%9C%93&q=1.7.2-1.5.4&type=

Deleting LB deployment does not get recreated

Watch Service, Deployment, DaemonSet deletion
Undo delete, if the source ingress exists.

Validate Ingress

Make sure crt & key have proper pem format.
Multiple hosts using same port for TCP ingress

Use alpine as the base image for haproxy

Support user provided annotations

As #100 notes, it will be useful for users to be able to apply annotations on HAproxy service and/or Deployment. Users can give a configmap with their custom annotations that we can use. Users can apply the following annotation to ingress:
ingres.appscode.com/annotations: <user-provided-cfgmap-name>

data:
  svc: |
  {
    "a/s1": "v1",
    "b/s2": "v2",
  }
  pods: |
  {
    "u/up1": "v1",
    "w/p2": "v2",
  }
kind: ConfigMap
metadata:
  name: <user-provided-cfgmap-name>
  namespace: <same-as-ingress>

The json object under svc key will be applied to service running in front of HAproxy. The json object under pods key will be applied to pods (Deployment/ DaemonSet) running HAproxy. This will allow users to use full spectrum of keys in annotations.

The keys will be filtered to remove any ingress.appscode.com/ keys, since those should be applied to ingress directly.

We should watch these configmaps so that they are dynamically updated. This can be done using a UpdateAnnotations mode.

I think the configmaps should be the vector for user annotations. Using secrets does not make sense, since annotations will be ultimately visible to users.

unable to decode "voyager/certificate.yaml": no kind "Certificate" is registered for version "appscode.com/v1beta1"

So I followed the getting started guide, but am running into some errors when trying to deploy. First, my yamls:

resources.yaml

# following https://github.com/appscode/voyager/blob/master/docs/user-guide/README.md
apiVersion: extensions/v1beta1
kind: ThirdPartyResource
metadata:
  name: ingress.appscode.com
description: "Extended ingress support for Kubernetes by appscode.com"
versions:
  - name: v1beta1

--- 
apiVersion: extensions/v1beta1
kind: ThirdPartyResource
metadata:
  name: certificate.appscode.com
description: "A specification of a Let's Encrypt Certificate to manage."
versions:
  - name: v1beta1

ingress.yaml

apiVersion: appscode.com/v1beta1
kind: Ingress
metadata:
  name: voyager-ingress
  namespace: default
spec:
  rules:
  - host: mydomain.com
    http:
      paths:
      - path: "/*"
        backend:
          serviceName: service1
          servicePort: '8282'
  - host: myotherdomain.com
    http:
      paths:
      - path: /*
        backend:
          serviceName: service2
          servicePort: '8484'

deployment.yaml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    run: appscode-voyager
  name: appscode-voyager
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      run: appscode-voyager
  template:
    metadata:
      labels:
        run: appscode-voyager
    spec:
      containers:
      - name: appscode-voyager
        args:
        - --cloud-provider=gke
        - --cluster-name=myclustername
        image: appscode/voyager:1.5.1
        imagePullPolicy: Always

certificate.yaml

apiVersion: appscode.com/v1beta1
kind: Certificate
metadata:
  name: voyager-cert
  namespace: default
spec:
  domains:
  - mydomain.com
  - myotherdomain.com
  email: [email protected]
  provider: googlecloud
  providerCredentialSecretName: test-gcp-secret

One thing of note is that I'm not sure what the providerCredentialSecretName should be. I'm using the google container engine, but wasn't able to find exactly what should go in there, but I don't think that's causing the issue I'm seeing.

So anyways, I use
kubectl apply -f directory_containing_all_these_files/

and the output I get is:

deployment "appscode-voyager" configured
thirdpartyresource "ingress.appscode.com" configured
thirdpartyresource "certificate.appscode.com" configured
unable to decode "voyager/certificate.yaml": no kind "Certificate" is registered for version "appscode.com/v1beta1"
unable to decode "voyager/ingress.yaml": no kind "Ingress" is registered for version "appscode.com/v1beta1"

Is there a step I skipped?

Run L7 ingress on non-standard ports

Test case:

HTTP on ports other than 80 & 443.
443: terminate SSL, 80: redirects to 443. (noSSL)
HTTP (noSSL on port 443), application itself terminates SSL.

Record events against TPR

Use EventRecorder to record events.

Errors
Success

What is the purpose of the --cloud-provider and the --cluster-name flag?

https://github.com/appscode/voyager/blob/master/docs/user-guide/README.md#deploy-controller shows --cloud-provider and --cluster-name being set, but why is this needed? If this tool is running within the cluster, why does it care what provider it's running on and what the cluster name is?

Allow free form HTTP rewriting

Failing to deploy

I have been trying to deploy voyager to give it a try and seem to be failing at it. I started with kubernetes 1.4.8, but failed. I gave it a try with a fresh cluster (1.5.2) deployed by kops with basically all defaults, heapster and dashboard. Got the same problem:

$ kubectl apply -f https://raw.githubusercontent.com/appscode/k8s-addons/master/api/extensions/ingress.yaml
thirdpartyresource "ingress.appscode.com" created
$ kubectl apply -f https://raw.githubusercontent.com/appscode/k8s-addons/master/api/extensions/certificate.yaml
thirdpartyresource "certificate.appscode.com" created
$ cat ingress-voyager/deployment.yml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    run: appscode-voyager
  name: appscode-voyager
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      run: appscode-voyager
  template:
    metadata:
      labels:
        run: appscode-voyager
    spec:
      containers:
      - name: appscode-voyager
        args:
        - --cloud-provider=aws
        - --cluster-name=tamas-k8s
        image: appscode/voyager:1.5.0
        imagePullPolicy: Always
$ kubectl apply -f ingress-voyager/deployment.yml
deployment "appscode-voyager" created
$ kubectl get thirdpartyresource
NAME                       DESCRIPTION                                                 VERSION(S)
certificate.appscode.com   A specification of a Let's Encrypt Certificate to manage.   v1beta1
ingress.appscode.com       Extended ingress support for Kubernetes by appscode.com     v1beta1
$ kubectl get po
NAME                                READY     STATUS    RESTARTS   AGE
appscode-voyager-3269309913-glhpd   1/1       Running   0          4m

Everything get's deployed from what I can tell, however the logs of the pod indicated an error:

2017-02-24T14:42:14.767629922Z W0224 14:42:14.767468       1 client_config.go:481] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2017-02-24T14:42:14.832700877Z E0224 14:42:14.832589       1 reflector.go:199] github.com/appscode/voyager/vendor/github.com/appscode/k8s-addons/pkg/watcher/objects.go:138: Failed to list *api.Alert: the server could not find the requested resource
2017-02-24T14:42:15.834770679Z E0224 14:42:15.834656       1 reflector.go:199] github.com/appscode/voyager/vendor/github.com/appscode/k8s-addons/pkg/watcher/objects.go:138: Failed to list *api.Alert: the server could not find the requested resource

(this goes on forever)

And then when trying to deploy an ingress:

$ cat jenkins/ingress-voy.yml
apiVersion: appscode.com/v1beta1
kind: Ingress
metadata:
  name: jenkins-ingress-voy
  namespace: jenkins
spec:
  rules:
  - host: jenkins.tamas.--omitted--
    http:
      paths:
      - path: "/"
        backend:
          serviceName: jenkins-ui
          servicePort: ui
$ kubectl apply -f jenkins/ingress-voy.yml
error: unable to decode "jenkins/ingress-voy.yml": no kind "Ingress" is registered for version "appscode.com/v1beta1"

Did I miss something or are there extra steps?

Truly Seamless Reloads with HAProxy

https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/

Cert controller issues

Cert controller hard codes kubed name
Cert controller waits until Ingres.Status.LoadBalancer_IP is set
all the annotations and their parsing move to api pkg https://github.com/appscode/voyager/blob/master/pkg/certificate/controller.go#L28

Specify different services in a backend with weights

Add label to Pod for weights ingress.appscode.com/weight:<N>.
Cache pods for checking labels

Improve test suite

helm chart

used to be the helm chart to install voyager, but I see it is gone.
any plans to add it back?

Test that previously open NodePort is not reassigned

Update service in NodePort & LoadBalancer mode

Update documentation for nodeSelector cleanup

#18

Support health checks

Health checks:
https://www.haproxy.com/doc/aloha/7.0/haproxy/healthchecks.html

https://blog.sentry.io/2017/03/01/dodging-s3-downtime-with-nginx-and-haproxy.html

Slack channel token_revoked

I stumbled across voyager today, and thought the features looked really cool! I was hoping to get it set up, but ran into some bugs while following the user guide. Unfortunately, it looks like the slack channel is closed, because when I try to get an invite it says that the token is revoked.

Various clean ups

Use ingress.appscode.com/daemon.nodeSelector and remove ingress.appscode.com/daemon.hostname
Don't pass stats password as label. Rather pass a secret name as label. The keys can be

username: xyz
password: abc

Use pod hostname in HAProxy config instead of ip

The benefit of this approach is not clear.

Test SNI support

Use AWS ELB Proxy Protocol

Currently, when the CLOUD_PROVIDER is set to aws, a new Service is created for the Ingress of type LoadBalancer by default.

The behavior I desire is for the LoadBalancer Service to use the "service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*" annotation to enable the Proxy Protocol on the AWS ELB, so that the proper headers like X-Real-IP and X-Forwarded-For are set correctly.

Here are my deployments:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: voyager-operator
  namespace: default
  labels:
    run: voyager-operator
spec:
  replicas: 1
  selector:
    matchLabels:
      run: voyager-operator
  template:
    metadata:
      labels:
        run: voyager-operator
    spec:
      containers:
      - name: voyager-operator
        image: appscode/voyager:1.5.4
        args:
        - --cloud-provider=$(CLOUD_PROVIDER)
        - --cluster-name=$(CLUSTER_NAME)
        - --v=3
        ports:
        - containerPort: 1234
          name: zero
          protocol: TCP
        env:
        - name: CLOUD_PROVIDER
          value: aws
        - name: CLUSTER_NAME
          value: mcclusterface

---

kind: Service
metadata:
  name: voyager-operator
  namespace: default
  labels:
    run: voyager-operator
spec:
  ports:
  - name: zero
    port: 1234
    targetPort: zero
  selector:
    run: voyager-operator

Track Kube's refactoring cloud provider API

Voyager adds a new Firewall() interface to Kubernetes CloudProvider api. This is a tracking bug to update our modifications.
kubernetes/community#128

AWS ALB/ NLB

Comparison: https://aws.amazon.com/elasticloadbalancing/details/

http://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html

Benefits:
http://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html#application-load-balancer-benefits

https://jve.linuxwall.info/ressources/taf/haproxy-aws/

expose NodePort like functionality to Ingress

When you are using Voyager with CLOUD_PROVIDER=null because you are using it on baremetal, or maybe DigitalOcean, Voyager allows you to use these annotations:

ingress.appscode.com/type: Daemon
ingress.appscode.com/daemon.nodeSelector: "kubernetes.io/hostname=foo"

Then when the daemonset starts in the selected node it automatically binds to the tcp port 80, that makes obviously sense, but it would be great if the user is able to use NodePort as well as an alternative.

For example in our case we have a four node cluster in our hosting provider so I only have 4 available ports to use with Voyager but I have thousands of free ports that I would like to use with Voyager and Nodeport.

Thanks!

Ensure pods are deleted before deleting RC / Deployment

Expose HAProxy stats to prometheus

https://github.com/appscode/haproxy_exporter

@sadlil , I think we can take the same approach we are taking with k8sdb regarding exporters. A single exporter running in the same namespace as the operator can take care of exposing these metrics for all Haproxys.

Cross Namespace Service Support

Hi there,

I was wondering if you could explain how "cross namespace service support" noted in the project's README works. I'm particularly interested in understanding this because I would like to know if I can use this ingress controller to do weighted load balancing to a set of backends in different namespaces. Essentially, I would like to siphon off a percentage of production traffic to services in separate, isolated namespaces for testing. Would something like this be possible? Does Voyager support customization of the HAProxy template (for example, to include weights in the backends section of the config?

Thanks!

Support HTTP/2 in http mode

Currently HAProxy supports HTTP/2 only in tcp mode. This is already supported in Voyager. See here: http://discourse.haproxy.org/t/http-2-support-in-1-7/927

This is blocked on HAProxy supporting HTTP/2 in http mode.

Change how stats work

Stats should be exposed by a ClusterIP type by service named as <ingress-name>-stats. This will ensure that stats are not internet accessible. This is needed, since stats endpoint is not secured by SSL, even though we have a way to set password.
Since stats are not internet accessible any more, using secrets should be optional.
Give users option to select stats port using ingress.appscode.com/stats.port. This will allow users to use port 1936 for their own services (if they want to).

Automatically update firewall when nodeSelector is changed.

Fix ALPN negotiation

curl -v https://api.appscode.info:3443/_appscode/api/health/json says:
ALPN, server did not agree to a protocol

https://tools.keycdn.com/http2-test check for https://api.appscode.info:3443/_appscode/api/health/json says ALPN not enabled.

If I open a LoadBalancer type service directly for apiserver, KeyCDN test shows that it supports ALPN:
https://104.197.254.187/_appscode/api/health/json

Compare this to a direct GO server: https://my-ip.space/index.json

$ curl -v  https://my-ip.space/index.json
*   Trying 67.205.171.99...
* Connected to my-ip.space (67.205.171.99) port 443 (#0)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* found 697 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* 	 server certificate verification OK
* 	 server certificate status verification SKIPPED
* 	 common name: my-ip.space (matched)
* 	 server certificate expiration date OK
* 	 server certificate activation date OK
* 	 certificate public key: RSA
* 	 certificate version: #3
* 	 subject: CN=my-ip.space
* 	 start date: Fri, 30 Dec 2016 10:19:00 GMT
* 	 expire date: Thu, 30 Mar 2017 10:19:00 GMT
* 	 issuer: C=US,O=Let's Encrypt,CN=Let's Encrypt Authority X3
* 	 compression: NULL
* ALPN, server accepted to use http/1.1

Current hypothesis is cipher suite includes blacklisted ciphers. Need more research. http://http2.github.io/http2-spec/#rfc.section.9.2.2

Test NodePort mode

Document 1.5.5 milestone features

Update voyager docs

Should all hosts be passed to EnsureLoadBalancer

Support use of field spec.loadBalancerSourceRanges on Services of type LoadBalancer

AWS, GCE and GKE support use of the spec.loadBalancerSourceRanges field on Services of type LoadBalancer to configure the firewall for the load balancer created by Kubernetes.

apiVersion: v1
kind: Service
metadata:
  annotations:
    ingress.appscode.com/name: frontend
    ingress.appscode.com/type: LoadBalancer
  name: voyager-frontend
spec:
...
  type: LoadBalancer
  loadBalancerSourceRanges:
  - 130.211.204.1/32
  - 130.211.204.2/32

https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/

Voyager pod is restarting itself when attached backend pod restarts

I talked with @tamalsaha in Slack about this, basically, when I delete the attached pod, the Voyager pod terminates too and it keeps restarting for a while until it finally keeps running.

skuda@skuda ~ $ kubectl get pods -o wide | grep user
mysql-user-0                            2/2       Running   0          2d        10.200.65.19   master-03
mysql-user-1                            2/2       Running   0          1h        10.200.75.4    master-02
voyager-mysql-user-ingress-rd3gn        1/1       Running   0          1h        10.0.0.3       master-03

skuda@skuda ~ $ kubectl delete pod mysql-user-0
pod "mysql-user-0" deleted

skuda@skuda ~ $ kubectl get pods -o wide | grep user
mysql-user-0                            2/2       Terminating   0          2d        10.200.65.19   master-03
mysql-user-1                            2/2       Running       0          1h        10.200.75.4    master-02
voyager-mysql-user-ingress-rd3gn        0/1       Terminating   0          1h        10.0.0.3       master-03

This is the yaml file related to this setup:

apiVersion: apps/v1beta1
kind: StatefulSet
metadata:
  name: mysql-user
spec:
  serviceName: mysql-user-headless
  replicas: 2
  template:
    metadata:
      labels:
        app: mysql-user
      annotations:
        pod.alpha.kubernetes.io/initialized: "true"
        
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 10
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 1
              podAffinityTerm:
                labelSelector:
                  matchExpressions:
                  - key: "app"
                    operator: In
                    values: 
                    - mysql-user-headless
                topologyKey: "kubernetes.io/hostname"

      containers:
      - name: mysql
        imagePullPolicy: Always
        image: percona:5.7
        resources:
          requests:
            memory: "4Gi"
            cpu: "2"
        ports:
        - containerPort: 3306
          name: mysql
        volumeMounts:
        - name: config-volume
          mountPath: /etc/mysql/mysql.cnf
          subPath: mysql.cnf
        - name: config-volume
          mountPath: /etc/mysql/conf.d/extra.cnf
          subPath: extra.cnf
        - name: data
          mountPath: /var/lib/mysql
        - name: local-fs
          mountPath: /tmp
        env:
        - name: MYSQL_ROOT_PASSWORD
          value: percona
        readinessProbe:
          tcpSocket:
            port: 3306
          initialDelaySeconds: 10
          periodSeconds: 30
        livenessProbe:
          tcpSocket:
            port: 3306
          initialDelaySeconds: 20
          periodSeconds: 30
      - name: phpmyadmin
        image: phpmyadmin/phpmyadmin:4.6
        ports:
        - containerPort: 80
          name: phpmyadmin
        resources:
          requests:
            memory: "500Mi"
            cpu: "500m"
        env:
        - name: PMA_HOST
          value: 127.0.0.1
        readinessProbe:
          httpGet:
            path: /index.php
            port: 80
          initialDelaySeconds: 10
          periodSeconds: 30
        livenessProbe:
          httpGet:
            path: /index.php
            port: 80
          initialDelaySeconds: 20
          periodSeconds: 30
      volumes:
      - name: config-volume
        configMap:
          name: mysql-user-configmap
      - name: local-fs
        emptyDir: {}
  volumeClaimTemplates:
  - metadata:
      name: data
      annotations:
        volume.beta.kubernetes.io/storage-class: fastio
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 32Gi


---

apiVersion: v1
kind: Service
metadata:
  name: mysql-user-headless
  labels:
    app: mysql-user
spec:
  ports:
  - port: 3306
    targetPort: 3306
    name: mysql
    protocol: TCP
  - port: 80
    targetPort: 80
    name: phpmyadmin
    protocol: TCP
  clusterIP: None
  selector:
    app: mysql-user

---

apiVersion: appscode.com/v1beta1
kind: Ingress
metadata:
  name: mysql-user-ingress
  annotations:
     ingress.appscode.com/type: Daemon
     ingress.appscode.com/daemon.nodeSelector: "kubernetes.io/hostname=master-03"
spec:
  rules:
  - host: phpmyadmin.local
    http:
      paths:
      - path: '/1'
        backend:
          hostNames:
          - mysql-user-0
          serviceName: mysql-user-headless
          servicePort: '80'
          rewriteRule:
          - ^(GET|POST|HEAD)\ /1/(.*)     \1\ /\2
      - path: '/2'
        backend:
          hostNames:
          - mysql-user-1
          serviceName: mysql-user-headless
          servicePort: '80'
          rewriteRule:
          - ^(GET|POST|HEAD)\ /2/(.*)     \1\ /\2

Thanks!

Support full spectrum of HAProxy rules

Request:
https://www.haproxy.com/doc/aloha/7.0/haproxy/http_rewriting.html#rewriting-http-requests

Response:
https://www.haproxy.com/doc/aloha/7.0/haproxy/http_rewriting.html#rewriting-http-responses

Health checks:
https://www.haproxy.com/doc/aloha/7.0/haproxy/healthchecks.html

Support StatefulSet pod names in Voyager

Instead of using Pod endpoints, use their stable DNS names if possible.

- backend:
    statefulSetName: jenkins-service
    statefulSetPort: "80"

Ensure HAproxy running when endpoints changes.

Rename Daemon type to HostPort

Voyager can operate in 2 modes: LoadBalancer & Daemon. Soon there will be a mode for NodePort. In that light, we should rename Daemon to HostPort so that these modes describe variations of a service used to expose HAProxy.

TODOs:

Add HostPort type. Alias it to Daemon
Update docs to rename Daemon to HostPort
Mention in the changelog.

Enable GKE

Add GKE to the list of supported cloud providers. It should be same as GCE.

https://github.com/appscode/voyager/blob/master/pkg/controller/ingress/handler.go#L44

ref: https://www.reddit.com/r/kubernetes/comments/62cobg/custom_ingress_controller_on_googe_container/

voyagermesh / voyager Goto Github PK

voyager's Introduction

Voyager

Ingress

Certificate

Installation

Using Voyager

Contribution guidelines

Acknowledgement

Support

voyager's People

Contributors

Stargazers

Watchers

Forkers

voyager's Issues

Recommend Projects

Recommend Topics

Recommend Org