I Cannot SSH Into My Server Anymore (And That’s Fine)

To kick off 2026, I had clear objectives in mind: decommissioning my trusty VPS and setting up its successor. Embracing a complete paradigm shift, I built myself a container-centric, declarative, and low-maintenance setup for the years to come.

For years, my VPS had been my reliable workhorse, hosting various projects and services that I relied on daily. It was a staple of my digital life, providing a stable foundation for my online presence. However, as technology evolves, so too must our infrastructure. The time had come to modernize and streamline my setup, moving away from the traditional VPS model towards a more efficient and scalable solution.

The decision to decommission the VPS was not made lightly. It represented years of investment, both in terms of time and resources. Yet, the prospect of a more dynamic and adaptable environment beckoned. Containers, with their lightweight and portable nature, offered a compelling alternative. By containerizing my applications, I could achieve greater flexibility, easier scaling, and faster deployment.

The shift to a container-centric setup required a significant overhaul of my infrastructure. I began by evaluating the various container orchestration platforms available. Docker Swarm, Kubernetes, and Nomad were all considered, each with its own strengths and ecosystem. Ultimately, I settled on Kubernetes, drawn by its robustness, scalability, and wide adoption in the industry.

Setting up a Kubernetes cluster from scratch was a daunting task. I started with a local development environment, gradually building up my knowledge and confidence. Once I felt ready, I moved on to the cloud, leveraging services like Google Kubernetes Engine (GKE) for a managed, production-ready solution.

As I migrated my applications to containers, I embraced a declarative approach. This meant defining my infrastructure and services using configuration files, rather than relying on manual setup and scripts. Tools like Helm and Kustomize proved invaluable in managing my Kubernetes resources, allowing me to version control my configurations and apply them consistently across environments.

The transition was not without its challenges. Debugging containerized applications can be more complex than traditional VPS setups, and I faced several hurdles along the way. However, the benefits quickly became apparent. My applications were now more resilient, easier to maintain, and capable of scaling seamlessly in response to demand.

One of the most significant advantages of this new setup was the reduced maintenance overhead. With containers, I no longer needed to manage the underlying VPS infrastructure. Instead, I could focus on my applications, confident that the underlying system would handle scaling and resource management efficiently.

The decision to decommission my VPS also freed me from the constraints of a fixed, long-term commitment. With a container-centric setup, I could easily adjust my resource allocation as needed, paying only for what I used. This flexibility was particularly appealing in an era of rapidly changing needs and budgets.

As I look back on this journey, I realize that the loss of SSH access to my VPS was not a setback, but rather a natural evolution. It marked the end of an era, symbolizing the transition to a more modern and efficient way of working. While I may miss the familiar command line interface of my old VPS, I am excited about the possibilities that lie ahead.

In the end, the shift to a container-centric, declarative setup has not only improved the performance and scalability of my infrastructure but has also enhanced my productivity and flexibility. It has taught me the value of embracing change and adapting to new technologies, ensuring that my digital presence remains relevant and robust in an ever-changing digital landscape.