Anders Johnsen

Co-Founder & CTO @rig_dev

[Rig.dev @Rig_dev]

One of the biggest inventions in software must be the Undo button. Being able to undo an operation is what gives us comfort when taking ownership, knowing already before you begin, how to mitigate any mistake you may accidentally make.

When it comes to deploying software, it becomes even more relevant. A single character is enough to impact your environments, may it be staging or production. And not knowing what part of your change impacted the system means you have to actually understand the impact before you can mitigate it.

This is one of the reasons the Rig Platform embraces rollback as a core feature. All changes made through our tools are possible to roll back, no matter if it’s a new image, network or environment variables. Rollback is the Undo button of platform engineering!

[Rig.dev @Rig_dev]

Day 2 Operations in a DevEx setting is complicated within Platform Engineering. Introducing Kubernetes to an organization can, for many, be a big, daunting task. Once this is accomplished, a new set of challenges emerges. One of these is the cognitive overload that engineers face when dealing with their services in Kubernetes.

At https://t.co/dImOTiF3hj, we can focus solely on making Day 2 Operations on Kubernetes a seamless experience. Our platform offers a simple yet powerful feature that allows developers to confidently deploy changes to their services. They can observe the changes taking effect and oversee the process without needing to understand every Kubernetes primitive.

... and if anything goes wrong, simply do a Rollback.

This is, among other things, what enables developers to obtain end-to-end application ownership, which is how you truly become successful as a company that has committed to using Kubernetes.

[Rig.dev @Rig_dev]

Helm Charts are great for installing an application, but that is usually not the hard part; maintaining an installation and keeping it running is. For this, developers should expect a better developer experience in 2024.

We've listed three of the major pitfalls for Helm Charts in a Platform Engineering setting below:

⛔️ After a Helm chart has been executed, the abstraction of the Helm chart steps into the background until the next time the developer needs to deploy. Developers must now look in Kubernetes for the current state when continuously working with their applications. This means they will need to understand the complexity that the helm chart has abstracted away, as it only provides abstraction at the time of deployment and not at runtime.

⛔️ Kubernetes APIs combined with Helm are powerful but complex. Helm doesn't make it unnecessary to understand the Kubernetes APIs, as it only provides abstraction at deploy time. This gets even worse if you force your engineers to own their Helm charts, as they then own the abstraction. On top of that, they also need to know the Go templating language, which is used in Helm.

⛔️ As you scale, standardization and migrations can become arduous tasks, particularly if developers are tasked with managing their own Helm charts. Introducing a new Kubernetes resource alongside existing services requires either instructing developers to modify their Helm charts or, in the best-case scenario, ensuring they adopt the updated Helm chart version.

At https://t.co/dImOTiF3hj, we believe that both developers and platform engineers deserve a better abstraction ⚡️

[Rig.dev @Rig_dev]

Thinking about migrating to Kubernetes? It might seem like a massive undertaking, but trust us — it's simpler than you think!

We recently got an inbound lead from a company looking to migrate to Kubernetes and wanted to evaluate Rig for their new self-hosted Kubernetes set-up on Hetzner using Rig.

We jumped on an intro call with them Friday, and they worked on setting up their Kubernetes clusters over the weekend. A few days later, they were fully migrated to Kubernetes and running in production using Rig.

If you're thinking about migrating to Kubernetes but are hesitant due to the complexity, we would love to have a chat and hopefully make it a more manageable project to embark on ⚡️

[Rig.dev @Rig_dev]

Most of our team will be at KubeCon in Paris next week, and we’re truly excited about a full week of discussing K8s, Platform Engineering and Developer Experience!

We would love to meet up to discuss best-practices and share notes on the space, so please drop us a comment or reach out directly to find some time 👋

[Kube Architect @K8sArchitect]

The Rig Platform offers an application platform for Kubernetes

Rig empowers developers to work in their environments with elevated application abstractions while leveraging Kubernetes's reliability, portability, and scalability

➜ https://t.co/feIfVx7wL2

[Rig.dev @Rig_dev]

When we work with companies, it's clear that GitOps has become a cornerstone in the cloud-native community.

We've worked on making the GitOps integration a seamless experience on the Rig platform.

Read our blog post on how we empower engineering teams to seamlessly integrate with Argo or Flux: https://t.co/Yv9D5xXEi2

Schedule a call with us to discuss platform engineering and developer experience: https://t.co/hRx3qhoDHJ

[Saumya Singh @saumya1singh]

🔥 Just launched @Rig_dev 🔥

→ Open-source feature-rich application platform
→ Powerful deployment engine
→ Automated build and rollouts
→ Beautiful admin dashboard
→ Must for backend and DevOps engineers

Thread 🧵

[Anders Johnsen @anders_johnsen]

⭐️ Github: https://t.co/5S6xaU430h
📖 Blog: https://t.co/zp7HMHCZLe

[Anders Johnsen @anders_johnsen]

Incredibly proud to be able to share that we’ve raised a $2.2m pre-seed round led by @byFounders , to accelerate us at @Rig_dev . Be sure to check out our blog and Github repo, I’ve shared the links in the comments.

[Anders Johnsen @anders_johnsen]

So excited to be part of this journey! 🚀

[Anders Johnsen @anders_johnsen]

Proud to say that Creandum has invested in our startup, Toitware!

[Bjarke Staun-Olsen @bjarkestaun]

Ladies and gentlemen: Toitware https://t.co/6IlUvNyMZW