Kubernetes Ingress for Spinnaker

ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: spinnaker-ingress
  namespace: spinnaker
  labels:
    k8s-addon: ingress-nginx.addons.k8s.io # change to your nginx controller
  annotations:
    kubernetes.io/tls-acme: "true" # tells the letsencrypt controller to watch this ingress
spec:
  tls:
  - hosts:
    - spinnaker.ops.hostname.com
    secretName: spinnaker-tls
  rules:
  - host: spinnaker.ops.hostname.com
    http:
      paths:
      - backend:
          serviceName: spinnaker-spinnaker-deck # do `kubectl get svc -n spinnaker | grep deck` to get your deck service name
          servicePort: 9000
      - backend:
          serviceName: spinnaker-spinnaker-gate # same applies here, but grep gate.
          servicePort: 8084

@joshuatalb helm chart for kube-lego has used nginx-ingress annotation instead of label k8s-addon, can you update the gist to reflect that?

EXAMPLE INGRESS YAML:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: example
  namespace: foo
  annotations:
    kubernetes.io/ingress.class: nginx
    # Add to generate certificates for this ingress
    kubernetes.io/tls-acme: 'true'
spec:
  rules:
    - host: www.example.com
      http:
        paths:
          - backend:
              serviceName: exampleService
              servicePort: 80
            path: /
  tls:
    # With this configuration kube-lego will generate a secret in namespace foo called `example-tls`
    # for the URL `www.example.com`
    - hosts:
        - "www.example.com"
      secretName: example-tls