We work with existing servers and Kubernetes clusters just as seamlessly as we build new environments from scratch. Whether you want us to take over a running platform or design a clean deployment, our onboarding process adapts to your needs.
Setting up the initial Bastion or VPN access typically takes only a few hours. The exact timeline depends mainly on how quickly the required network connectivity (firewall rules, routing, etc.) can be prepared on your side.
Once access is available:
This ensures fast, low-friction onboarding with minimal disruption.
For Kubernetes clusters - we could do "monitoring only" of an existing cluster. But you wouldn't benefit as much from KubeAid then - so our recommendation is to only do that for a shorter period - while we help design a new cluster setup, built on KubeAid - solving the issues we find in your current setup.
This includes installing our Kubernetes observability stack, configuring alerting, integrating Keycloak.
Once secure access is established, we perform a full evaluation of your current setup.
Our assessment covers:
We then collaborate with you to define a clear improvement roadmap and long-term operational plan.
Q: Your solution uses Puppet. If we plan to use our own Puppet agent for configuration management, could this cause any conflicts? If so, is there a recommended workaround?
Yes - you can run two Puppet agents in parallel, and we can assist you in setting this up safely so they do not interfere with each other.
However, our recommended approach is to use the LinuxAid Puppet setup (now called OpenVox, following the community fork). Using our Puppet setup provides several operational benefits listed here https://github.com/Obmondo/LinuxAid?tab=readme-ov-file#real-world-benefits
Importantly, both Puppet (LinuxAid/OpenVox) and the LinuxAid Prometheus monitoring stack can run entirely on your own hosts, under your control. We only require access when you want us to act as an extension of your operations team.
You can read more about the LinuxAid setup here