As you may have gathered from the title, I did NOT pass the CKA exam. The title is not some clickbait where I turn things around and explain how I passed the exam by doing X, Y, and Z. Nope, I failed. And failure is important. You learn more from your failures than your successes, as anyone who has tried to build a CI/CD pipeline or write a piece of code can attest. There’s always going to be a lot of red before you see a hint of green. In this post I want to talk about what I did to prepare, what I should have done, and what I plan to do before retaking the exam. Yes, dear reader, I am going to retake the exam and this time I will PASS!
2020 was… a year. Or more like a decade packed into a single year. Looking back at everything that happened, it seems both too much and not enough. Conferences were cancelled, schools were closed, Zoom proficiency spiked, and we all added several new words to our vocabulary. This post is not meant to rehash our shared trauma of 2020, but I need to at least acknowledge it as a driving factor for the year. At the beginning of the year, I set out some ideas and goals for the year. Let’s see how I fared given all that happened.
When I tried to fire up the dev instance to take Boundary for a test drive, I immediately got an unpleasant error:
Error creating dev database container: unable to start dev database with dialect postgres: could not start resource: : Post "http://localhost:2375/images/create?fromImage=postgres&tag=12": dial tcp [::1]:2375: connectex: No connection could be made because the target machine actively refused it.
I learned two things quickly:
- The dev server for Boundary uses Docker
- Boundary was having trouble talking to my install of Docker Desktop
If you’re in a similar boat, the fix is super easy! Open up the settings for Docker Desktop and tick this box:
Apply & Restart. That’s it.
Told you it was easy! Have fun playing with Boundary! I know I will.
I received a question recently on how to properly configure the AWS secrets engine on HashiCorp Vault to work with multiple AWS accounts. It took me a bit, but I did figure out how to do it and what the limitations are. In this post, I will break down how the secrets engine works and how to use it to dynamically create credentials across multiple AWS accounts using the
One year ago I decided to quit my consulting job at a respectable company and go rogue as the Founder and sole employee of Ned in the Cloud LLC. I thought that now might be a good time to reflect on how I feel about that decision a year in, how things are going personally and financially, and where I see the company going in the future. Come with me friend on this introspective journey to examine the real-world of an independent content producer.