Starting A Company Podcast

Wrote a post on how to start a podcast within a company at https://www.bootstrappers.mn/post/starting-a-company-podcast. It starts off:

The first time we do most things is usually the hardest. Once we get through one or two repetitions, most tasks get easier. About 400 podcast episodes in I’ve had a lot of failures that maybe just maybe anyone reading this article can avoid. So first, let’s look at why organizations make podcasts:

If it’s your cup of tea, read more at https://www.bootstrappers.mn/post/starting-a-company-podcast.

Macsysadmin 2020 Keynote Deck

I’ve decided that it would be awesome if anyone took any of my works and built on top of them. So I’m including the raw keynote deck and the pdf of the deck for my Macsysadmin talk this year. Please feel free to use the raw deck without attribution. No copyright or copyleft or any of that involved. <3

MacSysAdmin_API_PDFDownload
MacSysAdmin_API_KeynoteDownload

Kubectl: Echo and Check

After a virtual machine is provisioned and booted, we can echo the server and check that the cluster is deployed properly. Here, we’ll use a yaml file called kube_cluster_config604.yml (but your name may be different). That file should be in the directory with the cloned repo. We’ll kick it off with the kubectl binary. First, we’ll run a simple kubectl defining the –kubeconfig and then the yml file and apply a command that is an echo.yml (to see an example of that, check out( https://github.com/spinnaker/echo/blob/master/echo-web/config/echo.yml):

kubectl --kubeconfig kube_cluster_config604.yml apply -f echo.yml

We can then check the deployment using a get verb followed by pod, deployment, ingress, and sac:

kubectl --kubeconfig kube_cluster_config604.yml get pod
kubectl --kubeconfig kube_cluster_config604.yml get deployment
kubectl --kubeconfig kube_cluster_config604.yml get svc
kubectl --kubeconfig kube_cluster_config604.yml get ingress

In this case, the 604 postfix was created by a script that renames the yaml files when they’re checked in following a commit. The echo might also be version controlled (e.g. if we decide to use a different port or change one of the settings).