You’re remote, I’m remote, everybody is remote!

Remote developers desk

It’s been a crazy start to the year, and each month has been more ridiculous than the last! With a few of our clients being put into a state of frenzy as a result of the new working restrictions, we’re being asked some pretty strange questions. As a successful, remotely focused, engineering company, we are well-equipped for the challenges of an entirely remote workforce. Our clients on the other hand, not always! I’m hoping that this new shift will see a rise in companies agreeing to remote teams and the ‘work-from-home’ request being part of the norm where possible. We’ve compiled our top-tips for a successful switch to remote teams: Stick to a schedule – allow the team to create the schedule, but once it is agreed, stick to it. It’s more productive for the team, and also beneficial for […]

Kubernetes for multiple projects

Working with multiple projects at the same time using docker and kubernetes can get painful. Needing to remember contexts, configurations and the way that you interact with those can start to weigh down a local development process. Enter kubernetes namespaces Kubernetes namespaces allow you to separate a context out into multiple namespaces that all act like their own context. This is intended from the documentation to help segregate a kubernetes cluster based on environment (dev, staging, prod etc…) but it is also useful for local contexts. Check your current context is set to either docker-desktop or minikube (whichever you’re using) and create a new namespace: kubectl create namespace {project-name}. You can then list your config to identify your local context and user details with kubectl config view then from this create a new context that is tied to your local context […]