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.

I’ve upgraded WordPress to v5.5.1 let’s see how many issues I run into, every time I do an upgrade I find little crazy bugs.

I’ve passed my CKAD! this is a little delayed because I’ve been super busy.

It seems my mariadb container restarted which caused the site to become unstable, I killed both my front end pods and let k8s restart them and it all seems to be working right now, I need to do some investigation as to why the DB restarted.

Well I decided to upgrade my k8s cluster this morning to see what kind of damage I could inflict on the site, well a lot I took it down, I think a huge part of it is, I am only running 2 nodes and they are 2×4(2CPU, 4GB of RAM) and there just wasn’t enough resource once the rolling upgrade began. Also once the upgrade was complete my front end deployment was still broken I am running a service mesh and it seems the proxies timed-out waiting for resources, so the deployment was half up half down; luckily this was a simple fix, kubectl rollout restart deploy my_deploy again I think the core issue here is just not enough resource in the cluster.