I have been working for one of the major financial institutions of Australia for over two and a half years at this point as a consultant. To stay that long on a project isn’t common but I’ve enjoyed the challenges of this particular client.
I had been on a single project for about two years and it started to get a little stale when a colleague asked me to join his team as the Lead Engineer working with Google Cloud Platform (GCP).
The project was to uplift and migrate the foundational infrastructure as code (Terraform). The whole concept seemed so…
I’ve been working in Tech for the last 20 or so years. I would say my fascination started when I was a kid (10–11) and I had to install my first PC game in MS-DOS. I had nobody around who could instruct me but I found a manual and started reading. Eventually I was able to install it on the family PC and I became a super l33t h4x0r over night (… not quite).
This trend of reading computer manuals stuck and I eventually had a large bag of computer manuals I had collected and read. Despite this interest I…
If you’re seeing this article it’s probably for one of two reasons:
Either way, it’s a positive that you’re here. By the end of this article you’ll hopefully see how using “@here” is usually bad Slack etiquette and how it affects the team as a whole.
Let’s start by covering when you should use “@here”:
There are many places that workloads should be secured: In CI, within the cluster (securityContext & security policies), outside the cluster (firewalls), etc.
This article will specifically cover securing workloads with some Docker best practices and Kubernetes securityContext. These two sides go hand-in-hand to restrict inappropriate activities within the container.
Errors are stressful, especially when they aren’t meaningful and early.
In modern agile landscapes where developers and operations work together, there’s a big issue and that is the lack of clear communications.
How often do you see an error or failure only to think to yourself “but… I didn’t change anything!”, a ticket and a headache later you realize that the cluster has changed not your application and you weren’t notified. There are changes happening all the time, how would a platform engineer even notify a developer of so many changes?
It is essential that you export your data to somewhere other than GCP. Whilst GCP is an awesome cloud provider and the odds that Google goes bankrupt taking your workloads with it is extremely unlikely it is entirely possible that someone or some process (malicious or not), deletes your data in the cloud.
It’s for this situation that we need business continuity, disaster recovery, and all the other good buzz words that effectively mean, “to un-screw that which is effectively screwed”.
Programming is for everyone, not just “Developers”
I remember being in primary school when I was asked what I wanted to be when I “grow up”. I answered “Computer programmer” without even knowing what that meant.
Programming for a career is usually referred to as being a Developer. I’ve been programming in some fashion since I was a teenager but I’ve never had the job of “Developer”.
At this point in my career I’m a DevOps engineer/consultant. DevOps is more a methodology or a philosophy than a single job but in terms of a job, you could think of it…
I’ve written this article specifically for Go developers who are interested in CI within GCP — so if that’s you, you’re in the right place! I will intentionally skip steps along the way but where possible, I’ve included links to other tutorials or documentation on the steps excluded for those who would like to build or refresh their skills.
After you’ve gone through this tutorial, you should have the basic structure of a robust and secure CI pipeline for use with many different Go projects.
The software industry as a whole, has adopted build pipelines as a means to deliver…
He/Him, Nerdy husband/father. Photography enthusiast. Cloud/tech obsessed. Neurodivergent.