git-sync/demo
James Blair 104563fc47
Replace deprecated k8s registry references.
Problem: Previously all of Kubernetes' image hosting has been out of gcr.io. There were significant egress costs associated with this when images were pulled from entities outside gcp.  Refer to https://github.com/kubernetes/k8s.io/wiki/New-Registry-url-for-Kubernetes-(registry.k8s.io)

Solution: As highlighted at KubeCon NA 2022 k8s infra SIG update, the replacement for k8s.gcr.io which is registry.k8s.io is now ready for mainstream use and the old k8s.gcr.io has been formally deprecated and projects are requested to migrate off it. This commit migrates remaining references for kubernetes/git-sync to registry.k8s.io.
Signed-off-by: James Blair <mail@jamesblair.net>
2023-02-14 16:26:30 +13:00
..
blog remove broken analytics links 2021-07-03 23:51:53 +08:00
config Replace deprecated k8s registry references. 2023-02-14 16:26:30 +13:00
hugo remove broken analytics links 2021-07-03 23:51:53 +08:00
README.md remove broken analytics links 2021-07-03 23:51:53 +08:00

README.md

git-blog-demo

This demo shows how to use the git-sync sidekick container along side volumes and volumeMounts to create a markdown powered blog.

How it works

The pod is composed of 3 containers that share directories using 2 volumes:

  • The git-sync container clones a git repo into the markdown volume
  • The hugo container read from the markdown volume and render it into the html volume.
  • The nginx container serve the content from the html volume.

Usage

Build demo containers (Optional)

Build the demo containers, and push them to a registry

docker build -t <some-registry>/git-sync ..
docker build -t <some-registry>/hugo hugo/
docker push <some-registry>/hugo <some-registry>/git-sync

If you end up using a different registry, be sure to update config/deployment.yaml.

Create the pod and the service for the blog

kubectl create -f config

Open the service external ip in your browser