If you've worked with Docker or Kubernetes for any amount of time, you've probably done something like this:
- SSH into a server
- Check running containers
- Copy a container ID
- Restart a service
- View logs
- Repeat on another server
It works.
But after doing it hundreds of times, I started wondering:
Why am I still managing infrastructure almost entirely through the terminal for common day-to-day operations?
Don't get me wrong—I love the CLI. It's incredibly powerful.
The problem is that many operational tasks don't necessarily need to be command-line driven.
The Pain
Imagine managing multiple environments.
Production.
Staging.
Development.
Different Docker hosts.
Several Kubernetes clusters.
Every time something needs attention, you're switching terminals, remembering commands, checking contexts, and hoping you're operating on the right environment.
Even experienced engineers occasionally run:
kubectl config current-context
...just to make sure they're not about to restart production.
What I Wanted
I wanted a single place where I could:
- Visualize my infrastructure
- Connect Docker hosts and Kubernetes clusters
- Inspect workloads
- Restart services
- Scale deployments
- View logs
- Execute common operations
...without replacing the CLI.
Instead, I wanted something that complements it.
Building InfraCanvas
That's why I built InfraCanvas.
The idea is simple:
Your infrastructure becomes visual.
Instead of remembering where everything lives, you can actually see it.
Servers, clusters, namespaces, pods, containers—they're all represented visually while still exposing the power you'd expect from native Docker and Kubernetes operations.
Rather than jumping between multiple terminals and dashboards, everything is accessible from one interface.
Things I'm Focusing On
Current areas I'm working on include:
- Docker host management
- Kubernetes cluster management
- Interactive infrastructure visualization
- Container logs
- Restart/start/stop operations
- Scaling workloads
- Secure remote connections
- RBAC support
- AI-assisted operations (still evolving)
The goal isn't to hide complexity.
It's to reduce unnecessary friction.
Lessons Learned
Building infrastructure software is very different from building a CRUD application.
You quickly run into challenges like:
- Authentication
- Secure remote execution
- Cluster permissions
- Different Kubernetes versions
- Docker API quirks
- Performance with large environments
- Real-time updates
Every feature teaches something new.
I'd Love Feedback
I'm still actively building InfraCanvas, and I'd genuinely appreciate feedback from people who manage containers or Kubernetes in production.
Some questions I'm especially interested in:
- What repetitive infrastructure task annoys you the most?
- Which operation do you wish required fewer commands?
- Would a visual control plane make your workflow better—or would you stick to the CLI?
I'm trying to build something that helps engineers rather than replacing the tools they already love.
I'd love to hear your thoughts.
Top comments (0)