Azure cloud engineering
Cloud platforms, designed and operated by the same hands
Cloudwalker IT is a senior cloud engineering practice — Azure delivery in-house, AWS through our 010 Consulting partnership. We also build and operate KrakenKey and Atomatize, so the patterns we recommend are ones we already use in production.
Live SaaS
KrakenKey
TLS certificate automation — one-time DNS setup, then 4-minute renewals.
Live SaaS
Atomatize
AI content repurposing — long-form into platform-ready posts.
Delivery partner
010 Consulting
AWS delivery partner. Joint engagements when work demands deep AWS.
Engineer credentials
Certified Expert
Azure DevOps + Architect Expert · CKA · Terraform · RHCSA.
What we do
Three focused services
Azure architecture and operations as the primary practice. AWS delivered jointly with 010 Consulting. Platform engineering and Managed Terraform across both clouds.
Primary practice
Azure Cloud Engineering
Architecture, migration, FinOps, and operations on Azure — anchored by Solutions Architect Expert and DevOps Engineer Expert credentials.
Partnership offering
AWS — with 010 Consulting
Joint engagements: Cloudwalker IT leads, 010 brings AWS-specialist hands. One contact, two firms' depth.
Cross-cloud capability
Platform Engineering & Managed Terraform
Pipelines, modules, state, drift detection. AKS and EKS clusters. CI/CD with GitHub Actions and Azure DevOps.
Insights
Latest from the practice
· 4 min read
Azure Bastion's AKS Tunneling Goes GA: The Jump Box Becomes Optional
Azure Bastion can now tunnel directly to a private AKS cluster's API server, no jump box required. Here's what the GA release changes and where it still falls short.
· 6 min read
CVE-2026-42880: Argo CD's ServerSideDiff Endpoint Leaks Kubernetes Secrets to Read-Only Users
A critical (CVSS 9.6) missing-masking flaw in Argo CD lets any authenticated user extract plaintext Kubernetes Secret values. Patches are out; here's what AKS operators need to know before they get to it.
· 5 min read
No ILB, No MultiSubnetFailover: Setting Up an Azure SQL AG Listener for Legacy Clients
How we configured a SQL Server Availability Group listener in Azure without an Internal Load Balancer for a client whose legacy application couldn't use MultiSubnetFailover=True -- and the SQL port binding issue that caught us off guard.
Begin a conversation
Engagements typically start with a short call to understand the problem. If our practice is the right fit, we will say so. If not, we will recommend someone better suited.
Get in touch