Microservices Deployment on Azure & OCI
Budget / Salary₹600–1,500
TypeFreelance project
LocationRemote
Posted2 hours ago
I already have the idea and the tech stack—what I still need is the actual public-code example and a fully automated way to run it in production. Your task is to pick (or suggest) a container-based microservices application from GitHub or any other public source, then deploy it to Kubernetes clusters running both on Microsoft Azure (AKS) and Oracle Cloud (OKE). No coding the service itself; the real focus is the Devops work.
Here is what the finished project should showcase for me:
• Automated deployment pipelines driven by Terraform and GitLab CI/CD. The pipeline must spin up every cloud resource, build the Docker images, push them to registries, apply Kubernetes manifests or Helm charts, and expose the services behind load balancers—end to end with one merge.
• Infrastructure as Code that is clean, parameterised and reusable. Terraform modules should cover networking, node pools, storage, autoscalers and any policies required for cost optimisation.
• Kubernetes orchestration best practices: rolling updates, health probes, PodDisruptionBudgets, horizontal/vertical pod autoscaling and secrets management.
• High availability and resilience across at least two availability zones in each cloud. The same GitLab pipeline should be able to deploy to either environment through variable switching.
• Built-in cost controls: cluster-autoscaler, spot node pools or pre-emptible shapes, and clear tagging so each microservice’s spend is traceable.
• Operational readiness: monitoring (Azure Monitor, OCI Logging & Monitoring), alerting rules, and a brief incident-response runbook describing how to triage common production issues.
Deliverables I expect:
1. A fork or link to the chosen open-source microservices repo.
2. Terraform code, GitLab CI/CD YAML and any shell scripts.
3. Kubernetes manifests/Helm charts tailored for AKS and OKE.
4. A markdown guide that explains setup, pipeline usage, rollback, and cost-saving knobs.
5. A short recorded demo or live walkthrough proving that a fresh environment can be built, deployed, scaled and torn down.
If this sounds like your everyday playground, let’s get it shipped.
Requirement is for poject discussion only for now, if find suitable will create with new project with expected deliverables.
Here is what the finished project should showcase for me:
• Automated deployment pipelines driven by Terraform and GitLab CI/CD. The pipeline must spin up every cloud resource, build the Docker images, push them to registries, apply Kubernetes manifests or Helm charts, and expose the services behind load balancers—end to end with one merge.
• Infrastructure as Code that is clean, parameterised and reusable. Terraform modules should cover networking, node pools, storage, autoscalers and any policies required for cost optimisation.
• Kubernetes orchestration best practices: rolling updates, health probes, PodDisruptionBudgets, horizontal/vertical pod autoscaling and secrets management.
• High availability and resilience across at least two availability zones in each cloud. The same GitLab pipeline should be able to deploy to either environment through variable switching.
• Built-in cost controls: cluster-autoscaler, spot node pools or pre-emptible shapes, and clear tagging so each microservice’s spend is traceable.
• Operational readiness: monitoring (Azure Monitor, OCI Logging & Monitoring), alerting rules, and a brief incident-response runbook describing how to triage common production issues.
Deliverables I expect:
1. A fork or link to the chosen open-source microservices repo.
2. Terraform code, GitLab CI/CD YAML and any shell scripts.
3. Kubernetes manifests/Helm charts tailored for AKS and OKE.
4. A markdown guide that explains setup, pipeline usage, rollback, and cost-saving knobs.
5. A short recorded demo or live walkthrough proving that a fresh environment can be built, deployed, scaled and torn down.
If this sounds like your everyday playground, let’s get it shipped.
Requirement is for poject discussion only for now, if find suitable will create with new project with expected deliverables.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.