Any Idiot ... (Page 2)

Building my own images

I’d finished my previous post [https://blog.ervine.org/2018/08/hello-world-2/] by having setup a gogs git repository instance on my k8s cluster and made this instance accessible to both my local network (HTTP) via an external HAProxy instance and to the wider Internet (HTTPS) through my router

gogs

Hello World!

In my last post [https://blog.ervine.org/2018/08/providing-a-backend/] I had created a gogs instance using a MariaDB backend running on my k8s cluster. I had finished up by making the gogs HTTP service available to my internal network using a NodePort service in k8s. To the router

clusterip

Providing a backend

Previously [https://blog.ervine.org/2018/08/hosting-a-git-repo/], I’d deployed a pod running an instance of gogs to provide a source control repository in which I would aim to store my k8s YAML files and my container image build files. Building a backend The next step I want to

git

Hosting a git repo

Having created a very simple container image [https://blog.ervine.org/2018/08/down-the-rabbit-hole/] (basic ARM based Alpine Linux 3.8) and pushed it to my own private container image registry [https://blog.ervine.org/2018/08/adding-a-container-image-registry/], the next next step to navigate is to provide a repository for

docker

Adding a container image registry

From the previous post [https://blog.ervine.org/2018/08/down-the-rabbit-hole/], I now had my 5 node k8s cluster, and had just built my own very basic container based on Alpine Linux 3.8 for the Raspberry Pi. The next step is to have this container available to my k8s

sport

Pre-Season Training

Tomorrow The end of the summer is approaching and that means that a new hockey season is approaching, which means the joy of pre-season training is upon me. Tomorrow in the afternoon heat and humidity of Hong Kong I get to find out if I’ve done enough running/fitness

containers

Down the rabbit hole

What’s next for the cluster? Having successfully installed a k8s cluster, the obvious question to ask is ‘what’s next?’ or ‘what do I do with this?’. There are plenty of options available here – basically anything that can run on a Raspberry Pi can be containerised and deployed as

kubernetes

More of a to-do list

Some items outstanding: * The wordpress instance is hosted the k8s cluster, and I should note down how it has been deployed on the cluster, and some of the pitfalls I found, so I can avoid them next time. * Next post should cover off the gogs [https://gogs.io/] instance that

k8s

Off and running ...

It’s alive Part of my job involves working withOpenShift [https://www.openshift.com/]– which is pretty cool, however, it’s also not very practical to have this set up as a physical lab environment. I have previously set this up in VMs, basically to have an environment to work