kind-examples

With the aim of using a Kubernetes in Docker (kind) cluster for local development, this has some examples and notes.

Set up a kind cluster exposing container ports using the kind.config.yaml which exposes the worker node on port 80 & 443.

kind create cluster --config kind.config.yaml

Note, although normally kind can create multiple worker nodes, when exposing ports via the kind.config.yaml, only one worker can be used, as Docker can only route to one container.

$ kubectl get nodes
NAME                 STATUS   ROLES    AGE   VERSION
kind-control-plane   Ready    master   11m   v1.16.1
kind-worker          Ready    <none>   10m   v1.16.1

Contour

Contour uses Envoy to expose kubernetes externally.

Either check out contour to get the contour.yaml files or use the single consolidated file from https://projectcontour.io/quickstart/contour.yaml

Check out contour and apply everything in examples/contour

# from the project site
# kubectl apply -f https://projectcontour.io/quickstart/contour.yaml
# or from a local repo clone
$ git clone https://github.com/projectcontour/contour
$ kubectl apply -f contour/examples/contour
namespace/projectcontour created
serviceaccount/contour created
configmap/contour created
customresourcedefinition.apiextensions.k8s.io/ingressroutes.contour.heptio.com created
customresourcedefinition.apiextensions.k8s.io/tlscertificatedelegations.contour.heptio.com created
customresourcedefinition.apiextensions.k8s.io/httpproxies.projectcontour.io created
customresourcedefinition.apiextensions.k8s.io/tlscertificatedelegations.projectcontour.io created
serviceaccount/contour-certgen created
rolebinding.rbac.authorization.k8s.io/contour created
role.rbac.authorization.k8s.io/contour-certgen created
job.batch/contour-certgen created
clusterrolebinding.rbac.authorization.k8s.io/contour created
clusterrole.rbac.authorization.k8s.io/contour created
role.rbac.authorization.k8s.io/contour-leaderelection created
rolebinding.rbac.authorization.k8s.io/contour-leaderelection created
service/contour created
service/envoy created
deployment.apps/contour created
daemonset.apps/envoy created

Verify all resources are up

kubectl -n projectcontour get pods,ds,deployments,services

Now you can add your own resources and front them with contour using contour's CRD HTTPProxy

See kuard-httpproxy.yaml as an example of a deployment of kuard with an HTTPProxy.

kubectl apply -f kuard-httpproxy.yaml

Monitor via:

kubectl get pods,svc,httpproxy -l app=kuard

This should show something like:

kubectl get po,svc,httpproxy -l app=kuard
NAME                         READY   STATUS    RESTARTS   AGE
pod/kuard-6b65d9d8b5-drpqc   1/1     Running   0          2m
pod/kuard-6b65d9d8b5-klzhf   1/1     Running   0          2m

NAME            TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
service/kuard   ClusterIP   10.98.159.229   <none>        80/TCP    2m

NAME                                     FQDN        TLS SECRET   STATUS   STATUS DESCRIPTION
httpproxy.projectcontour.io/root-kuard   localhost                valid    valid HTTPProxy

and then go to http://localhost:80 in a browser to see kuard.

Another good example that shows of using all the aspects of the Contour HTTPProxy, see the article "HTTPProxy in Action" on the projectcontour.io blog.

monitoring

See what Envoy is doing:

export ENVOYPOD=$(kubectl get pods -n projectcontour -l "app=envoy" -o jsonpath="{.items[0].metadata.name}") && kubectl -n projectcontour logs $ENVOYPOD -c envoy -f