- Makefile 55.2%
- Smarty 44.8%
| templates | ||
| .bumpversion.cfg | ||
| .gitignore | ||
| .helmignore | ||
| Chart.yaml | ||
| default.conf | ||
| Makefile | ||
| README.md | ||
| values.yaml | ||
Static Website
If you want to:
- Publish a web site
- The site is merely static HTML/CSS (i.e. no server-side components)
- You want to (occasionally) upload updates to the site
Then this chart might be for you.
This chart implements:
- A web server to serve your site
- A Kubernetes
Ingressresource to make your site available to the outside world - A
PersistentVolumeClaimto store your site files - A deployment with
scp/rsyncinstalled and SSH key-based access.
The idea: Once deployed, you can concentrate on geting the HTML/CSS "right"; you can use rsync to create/update the site contents.
Values
The documentation for the values this chart expects is in values.yaml - to get something basic working you only need to supply a few values - e.g.:
---
ingress:
dnsNames:
- www.example.com
rsync:
service:
type: LoadBalancer
annotations:
external-dns.alpha.kubernetes.io/hostname: sync.www.example.com
authorizedKeys: |
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOOCqHJInsGdv9dAsVqGMhs4qGjGTyS826AHS8bh9dak yourname@example.com
The exact values you need will probably be different :-)
Prerequisites
You must have a working Ingress Controller - the usual ingress-nginx will work nicely, and others will probably work too.
If you have
external-dns
installed, it can set up a DNS name for the rsync service according
to the external-dns.alpha.kubernetes.io/hostname annotation.
It helps if you have Cert-Manager
installed with a working ClusterIssuer - this will allow the ingress
annotation kubernetes.io/tls-acme: "true" to handle the SSL
certificate automatically. Without this, you need some other method
of obtaining an SSL certificate.