I moved fabianbrash.com from running on DOKS to running inside of an s3 bucket fronted by cloudfront, but why? Simple cost. DO has a great k8s offering but their last round of price increases meant that I would now be paying over $90/month for 3 small k8s nodes, and even with the fact that I deployed other APPS into the cluster, I just couldn’t justify the cost, so I switched. I am also going to look into how to host other APPS I make in the future, I do have access to internal k8s clusters, but I have no interest in opening those up to the outside world and deal with the security risks that come with that.

I’ve passed my CKA!!!

So I ran into an issue today, I was deploying TAP on a TKGm cluster on-prem and I went with one of the available t-shirt sizes for my nodes — After I deployed TAP I noticed that the buildservice kept failing so I started to do a little troubleshooting, and when I checked the events I noticed that their were errors regarding disk pressure on the nodes and the pods being evicted, and then I remembered that TAP requires a minimum of 70GB of disk space on the worker nodes and I only had 40GB.

So at my new job I’ve been learning TAP(Tanzu Application Platform) and as apart of that I’ve had to setup a domain so I can build new apps and serve them from that domain, so obviously I just picked a domain from a list of domains that I own, and the domain I chose was alexanderbrash.dev; simple enough, but then I noticed that when I tried to access the TAP GUI in Chrome or Firefox I was getting redirected to the https version of the site and of course I hadn’t setup any certs or anything I was just messing around, even if I used an incognito window or tab, same thing, every time I would go to http://tap-gui.

So I just had to renew my letsencrypt certificate for my VCSA and ran into a few issues and I wanted to write them down here, so I will go through creating the cert and adding it to your VCSA in the below blog post. I will assume you have certbot only installed on your machine Let’s create our cert certbot certonly -d myservice.domain.com --manual --preferred-challenges dns --agree-tos -m mail@mail.com Of course make changes as needed from the above command, then follow the instructions to add a TXT record to your DNS provider Now comes the tricky bit of assemblying the certificate in a way that your VCSA will accept it and not choke, the below blog helped out quite a bit.

It’s been a while since I’ve posted on here but I’ve been quite busy, I’ve started to study for my CKA, plus I’ve been doing some React/Next.js/Redux work. I’ve built a couple of apps and I’m hosting them on Vercel check them out below. Hulu 2.0 Tesla Clone I hope to add some more to the above list, one app I’m thinking about is building a crypto bank app using Next.

Well after thinking about migrating from Wordpress I’ve actually done it, I’ve migrated the blog over to Hugo a static site generator; I will have a full write up on the reasons behind me migrating off of Wordpress but for now I just wanted to write something quick and get the infra in place to make the move. More to come…

So I ran into an interesting issue today, I had provisioned a new k8s cluster using kubeADM but I replaced docker with containerD, everything was smooth and then I deployed prometheus and grafana using helm, and I noticed that I couldn’t connect grafana to prometheus I had installed istio so I thought that was the issue, maybe by default istio was messing with the pods network communication, but I also noticed that when I tried to install a dashboard from grafana I received an error, so the container couldn’t reach grafana.

So that didn’t take long, after only 24 hours I’ve run into my first issue thankfully the fix was simple. When I went to create a post or edit a post I kept seeing the following error message “Updating failed. Error message: The response is not a valid JSON response.” After some Googling around I found this thread https://wordpress.org/support/topic/updating-failed-error-message-the-response-is-not-a-valid-json-response-2/ scrolling down I found my answer, head back to admin settings & permalinks and re-save your settings I changed mine so WordPress can respond to API calls, well apparently something funky happens to those settings after the upgrade and you need to just hit the save button again.