Weekend walk and seemed fairly quiet, and some grey clouds so looks like it’s going to rain again soon….
Binding GCP Accounts to GKE Service Accounts with Terraform
Kubernetes uses Service Accounts to control who can access what within the cluster, but once a request leaves the cluster, it will use a default account. Normally this is the default Google Compute Engine account in GKE, and this has extremely high level access and could result in a lot of damage if your cluster is compromised.
In this article, I will be setting up a GKE cluster using a minimal access service account and enabling Workflow Identity.
Continue readingTraining in Quarantine – Day 282
Did my walk at normal time, and there seems to be more schoolkids out today. Perhaps more schoolkids are back at school now?
Training in Quarantine – Day 281
A nice walking weather, but my phone decided to reboot on me while I was walking, messing up my train of thought and pace.
Training in Quarantine – Day 280
Late walk as I had a meeting that lasted an hour past my normal end time, and it looks like it’s about to pour with rain…
Training in Quarantine – Day 279
Okay walking day, no need for hat and gloves, but rainy still
Training in Quarantine – Day 278
Another slightly later walk, and a bit tipsy to boot — it was Mother’s Day and we had a big lunch/dinner together.
Training in Quarantine – Day 277
Walked a bit later than normal today, was cold, but warmed up after about 1.5 km into the walk.
Training in Quarantine – Day 276
Comfortable walking weather
GitLab’s Default Branch Name
GitLab is now implementing a change to make the default branch “main” instead of “master”, following GitHub and Atlassian in ditching the “master/slave” namings due to their negative history.
It should be noted that this change this makes little difference to the functionality these sites provide, and to git repositories in general. Also, the default branch can be overridden.
When creating a blank initial repo in GitLab or GitHub (i.e. without a README.md file), the sites will prompt you to push code in using instructions such as this (GitLab haven’t yet implemented the master –> main change yet so it still shows master on their instructions)
git clone git@gitlab.com:username/example.git
cd example
touch README.md
git add README.md
git commit -m "add README"
git push -u origin master
But there’s nothing to stop you from doing something like
git push -u origin trunk
Instead of master at the time of pushing.
trunk is also one of the three folders used in Subversion Version Control as part of the recommended layout (trunk, tags, branches) — yes, I did use svn previously, along with Mercurial, Visual SourceSafe, and even cvs.
trunk is also a more logical sounding main branch as you have branches that lead into the trunk of a repo. And the leaves could be considered to be the tags.
While it is great that the big name hosting platforms are migrating away from the master branch idea, it should be noted that you didn’t have to have this default branch name originally, nor were you (or are you still) tied to using their choice of main branch name.

You must be logged in to post a comment.