Deploy your app to your own Kubernetes cluster.
Deploy application code from a connected Git repository to a new Amazon EKS cluster or an existing Kubernetes cluster. Review the setup and follow the deployment in Microtica.
- Demo project
- Staging
- Add service
Sample add-service flow for acme/catalog-service. The cluster step offers a Microtica-managed EKS cluster, a connected cluster and a shared cluster, with the catalog namespace selected. Beside it, the service's scaling settings set CPU and memory requests and limits and autoscale between 2 and 4 instances.
Kubernetes delivery
What you get
A deployed service with its build and deployment logs, environment context and runtime status.
What you bring
- A Microtica project, access to the application repository and a reachable Kubernetes cluster.
- You can also provision a new Amazon EKS cluster through Microtica.
How it works
Know what happens before you start.
- 01
Connect the code
Choose a starter or an existing GitHub, GitLab or Bitbucket repository. Review the required pipeline files that Microtica adds when they are missing.
- 02
Select the target
Choose the environment and cluster. Configure the application’s required inputs and review the service settings before starting.
- 03
Deploy and inspect
Start the deployment, follow the run and open the service to inspect health, logs and deployment history. Configure its domain and scaling as needed.
An existing cluster is a supported starting point
The connection guide covers clusters on cloud providers or on-premise. Your cluster must be reachable, and its API endpoint and service-account token are part of setup.
Existing code still needs preparation
The import flow uses a Microtica pipeline definition. Review repository changes, build requirements and application configuration rather than assuming an unchanged deployment process.
“Getting Kubernetes right was one of the trickiest parts of our cloud journey—until we found Microtica. The platform abstracted away the complexity while keeping us in control. Add in their exceptional support, and we had everything we needed to run our infrastructure like a seasoned DevOps team.”
Access and control
Review cluster permissions before connecting
The documented connection manifest grants the Microtica service account cluster admin access. An optional namespace association is available, but do not assume that setting alone reduces the manifest’s RBAC permissions.
Try it on one service.
Start free with a development project, or bring your setup to a demo.