A2lianto: removed "template:info"

2026-09-11T03:24:47Z

removed "template:info"

← Older revision		Revision as of 22:24, 10 September 2026
Line 1:		Line 1:
	= Kubernetes =		= Kubernetes =
	We are running a [https://kubernetes.io/ Kubernetes] cluster on-prem on Tahini and Teriyaki servers. Each member gets their own namespace in which they can deploy their applications.		We are running a [https://kubernetes.io/ Kubernetes] cluster on-prem on Tahini and Teriyaki servers. Each member gets their own namespace in which they can deploy their applications.

	{{Info\|If you wish to learn about how to operate a Kubernetes cluster, you may create your own cluster using software such as [https://k3s.io/ k3s]. If all you want to do is run some containerized apps, then we suggest that you use our cluster instead, since it has far more resources.}}

	== Account resource limits ==		== Account resource limits ==
Line 14:		Line 12:

	If you wish to acquire more resources, please send an email to the Systems Committee with a brief justification.		If you wish to acquire more resources, please send an email to the Systems Committee with a brief justification.

	{{Info\|LoadBalancer services are disabled because we handle external traffic through Traefik, which we manage ourselves. See [[#Exposing your app\|Exposing your app]] below.}}

	== Create a new namespace ==		== Create a new namespace ==

A2lianto: Created Kubernetes User Guide for new k3s cluster

2026-09-11T03:24:17Z

Created Kubernetes User Guide for new k3s cluster

New page

= Kubernetes =
We are running a [https://kubernetes.io/ Kubernetes] cluster on-prem on Tahini and Teriyaki servers. Each member gets their own namespace in which they can deploy their applications.

{{Info|If you wish to learn about how to operate a Kubernetes cluster, you may create your own cluster using software such as [https://k3s.io/ k3s]. If all you want to do is run some containerized apps, then we suggest that you use our cluster instead, since it has far more resources.}}

== Account resource limits ==
As of August 23, 2026, the per-namespace resource limits for each member are:

* 40 pods
* 10 jobs
* 10 cron jobs
* 25 GB of Persistent Volume Claims
* 5 NodePort services

If you wish to acquire more resources, please send an email to the Systems Committee with a brief justification.

{{Info|LoadBalancer services are disabled because we handle external traffic through Traefik, which we manage ourselves. See [[#Exposing your app|Exposing your app]] below.}}

== Create a new namespace ==
Log into a general-use machine and run the following:<pre>
ceo k8s account activate
</pre>This will create a new Kubernetes namespace with the name <code>csc-username</code>. A new kubeconfig file will be placed into <code>~/.kube/config</code>. Your kubeconfig points at your namespace by default, so all commands you run will land there unless you specify otherwise.

To verify that everything is working, run:<pre>
kubectl cluster-info
</pre>The output should look something like this:<pre>
Kubernetes control plane is running at https://129.97.134.5:6443
CoreDNS is running at https://129.97.134.5:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
</pre>

== Quickstart ==
Say you have a Dockerized app and the image is available on a public registry such as [https://hub.docker.com/ Docker Hub] or [https://quay.io/ Quay.io]. Here is the minimum you need to get your app running in the cluster.

First, create a Deployment:<pre>
kubectl create deployment demo --image=ctdalek/myapp --port=80
</pre>Replace <code>--image</code> and <code>--port</code> as needed.

If your app does not need to be publicly accessible, you are done. Otherwise, create a Service to expose your Deployment:<pre>
kubectl expose deployment demo
</pre>Then create an Ingress to expose the Service to the outside world:<pre>
kubectl create ingress demo --rule='ctdalek.k8s.csclub.cloud/*=demo:80'
</pre>Your app will be accessible at <code>https://ctdalek.k8s.csclub.cloud</code>. If you wish to use a custom domain, please contact the Systems Committee.

For non-web apps, use a NodePort instead of an Ingress. NodePorts are only accessible from on-campus.

== Further reading ==
Kubernetes is well documented, so we will not repeat it here:

* [https://kubernetes.io/docs/home/ Kubernetes documentation]
* [https://kubernetes.io/docs/tutorials/ Kubernetes tutorials]
* [https://kubectl.docs.kubernetes.io/guides/ kubectl guides]

You may also contact the [mailto:syscom@csclub.uwaterloo.ca Systems Committee] if something is not working the way you expect.

Kubernetes User Guide - Revision history

A2lianto: removed "template:info"

A2lianto: Created Kubernetes User Guide for new k3s cluster