Skip to content

Instantly share code, notes, and snippets.

@haproxytechblog
Last active November 23, 2020 11:57
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save haproxytechblog/f14974d148064e31809a9ab8efbefb1d to your computer and use it in GitHub Desktop.
Save haproxytechblog/f14974d148064e31809a9ab8efbefb1d to your computer and use it in GitHub Desktop.
Multi-tenant Kubernetes Clusters with the HAProxy Kubernetes Ingress Controller
apiVersion: v1
kind: Namespace
metadata:
name: dev
$ kubectl apply -f dev-namespace.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: my-configmap
namespace: dev
data:
foo: 'bar'
$ kubectl get configmaps --namespace=dev
$ kubectl get namespaces
NAME STATUS AGE
default Active 4m33s
dev Active 2m38s
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: dev-edit
namespace: dev # grants permissions within the "dev" namespace
subjects:
- kind: User
name: bob # permissions for a user named bob
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: ClusterRole
name: edit # read/write access
apiGroup: rbac.authorization.k8s.io
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: dev-edit
namespace: dev # grants permissions within the "dev" namespace
subjects:
- kind: Group
name: dev-group # permissions for the group
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: ClusterRole
name: edit # read/write access
apiGroup: rbac.authorization.k8s.io
$ kubectl apply -f dev-rolebinding.yaml
# Sign it with the cluster's CA certificate
# This creates bob.crt
$ openssl x509 -req -in bob.csr -CA ~/.minikube/ca.crt -CAkey ~/.minikube/ca.key -CAcreateserial -out bob.crt -days 1000
$ kubectl config set-credentials bob --client-certificate=bob.crt --client-key=bob.key
$ kubectl config set-context minikube-bob --cluster=minikube --user=bob
$ kubectl config use-context minikube-bob
$ kubectl get pods --namespace=dev
NAME READY STATUS RESTARTS AGE
app-66d9457bf5-vpbnw 1/1 Running 1 22h
$ kubectl get pods --namespace=default
Error from server (Forbidden): pods is forbidden: User "bob" cannot list resource "pods" in API group "" in the namespace "default"
$ kubectl config use-context minikube
$ helm install onlydev haproxytech/kubernetes-ingress \
--set-string "controller.extraArgs={--namespace-whitelist=dev}"
$ helm install onlydev haproxytech/kubernetes-ingress \
--set-string "controller.extraArgs={--namespace-whitelist=dev-team-a,--namespace-whitelist=dev-team-b}"
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: app-ingress
namespace: dev
spec:
rules:
- http:
paths:
- path: /app-service
backend:
serviceName: app-service
servicePort: 80
$ helm install intranet haproxytech/kubernetes-ingress \
--set controller.ingressClass=intranet
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: app-ingress-internal
namespace: default
annotations:
haproxy.org/ingress.class: "intranet"
spec:
rules:
- http:
paths:
- path: /app-service
backend:
serviceName: app-service-internal
servicePort: 80
apiVersion: v1
kind: ResourceQuota
metadata:
name: dev-resources
namespace: dev
spec:
hard:
requests.cpu: "1"
requests.memory: 1Gi
limits.cpu: "2"
limits.memory: 2Gi
$ kubectl apply -f dev-quota.yaml
$ kubectl describe resourcequota dev-resources -n dev
Name: dev-resources
Namespace: dev
Resource Used Hard
-------- ---- ----
limits.cpu 0 2
limits.memory 0 2Gi
requests.cpu 500m 1
requests.memory 50Mi 1Gi
# Create a certificate signing request with CN=bob and O=dev-group
# This creates bob.csr and bob.key
$ openssl req -newkey rsa:2048 -nodes -keyout bob.key -out bob.csr -subj "/CN=bob/O=dev-group"
$ cat <<EOF | kubectl apply -f -
apiVersion: certificates.k8s.io/v1beta1
kind: CertificateSigningRequest
metadata:
name: bob
spec:
request: $(cat bob.csr | base64 | tr -d '\n')
usages:
- digital signature
EOF
$ kubectl certificate approve bob
$ kubectl get csr bob -o jsonpath='{.status.certificate}' | base64 --decode > bob.crt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment