Need help with ingress?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

caddyserver
279 Stars 40 Forks Apache License 2.0 36 Commits 27 Opened issues

Description

WIP Caddy 2 ingress controller for Kubernetes

Services available

!
?

Need anything else?

Contributors list

Caddy Ingress Controller

This is the Kubernetes Ingress Controller for Caddy. It includes functionality for monitoring

Ingress
resources on a Kubernetes cluster and includes support for providing automatic HTTPS certificates for all hostnames defined in ingress resources that it is managing.

Cloud Provider Setup (AWS, GCLOUD, ETC...)

In the

charts
folder a Helm Chart is provided to make installing the Caddy Ingress Controller on a Kubernetes cluster straight forward. To install the Caddy Ingress Controller adhere to the following steps:
  1. Create a new namespace in your cluster to isolate all Caddy resources.
  kubectl create namespace caddy-system
  1. Install the Helm Chart.
  helm install \
    --namespace=caddy-system \
    --repo https://caddyserver.github.io/ingress/ \
    --atomic \
    --set image.tag=latest \
    mycaddy \
    caddy-ingress-controller

The helm chart create a service of type

LoadBalancer
in the
caddy-system
namespace on your cluster. You'll want to set any DNS records for accessing this cluster to the external IP address of this
LoadBalancer
when the external IP is provisioned by your cloud provider.

You can get the external IP address with

kubectl get svc -n caddy-system

Debugging

To view any logs generated by Caddy or the Ingress Controller you can view the pod logs of the Caddy Ingress Controller.

Get the pod name with:

  kubectl get pods -n caddy-system

View the pod logs:

kubectl logs  -n caddy-system

Automatic HTTPS

To enable automatic https via ingress controller using Let's Encrypt you can set the argument

ingressController.autotls=true
and the email to use
[email protected]
on the caddy ingress controller helm chart values.

Example:

when you execute the helm-chart installation.

Bringing Your Own Certificates

If you would like to disable automatic HTTPS for a specific host and use your own certificates you can create a new TLS secret in Kubernetes and define what certificates to use when serving your application on the ingress resource.

Example:

Create TLS secret

mycerts
, where
./tls.key
and
./tls.crt
are valid certificates for
test.com
.
kubectl create secret tls mycerts --key ./tls.key --cert ./tls.crt
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: example
  annotations:
    kubernetes.io/ingress.class: caddy
spec:
  rules:
  - host: test.com
    http:
      paths:
      - path: /
        backend:
          serviceName: test
          servicePort: 8080
  tls:
  - hosts:
    - test.com
    secretName: mycerts # use mycerts for host test.com

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.