Creating VMS using Digitalocean kubernetes
Budget: ₹1,500 – ₹15,000 INR
Title: - Creating vms using digitalocean kubernetes
Skills/tools - Kubernetes, DigitalOcean, Traefik
Requirement:
Each pod will be assigned a VM(virtual machine), each pod will be given a path in ingress, eg - /vm1, which can be accessed using hostname, eg, www.hostname.com/vm1.
When a new pod is created and ingress rule is added to access the pod, the update to ingress rule should not disrupt the working/availability of the existing pods and
the newly added pod and path should be available for access without any restart.
Acceptance Criteria:
1. Setup digitalocean cluster.
2. Setup traefik proxy.
3. Deploy pods with different resources (cpu, memory, storage) size vms, servies, ingress.
4. Set up dns service.
5. Access and run the vm from pods.
6. When multiple vm are running.
7. Add new pods, services and update ingress with new rules/path.
8. Adding/updating new pods/services/ingress should not disrupt the current running vms.
9. Newly added pods can be accessed without having to restart.
10. Give a demo on above.
11. Setup the whole thing in the given environment.
12. Any errors if occurs should troubleshoot and fix it.
Skills/tools - Kubernetes, DigitalOcean, Traefik
Requirement:
Each pod will be assigned a VM(virtual machine), each pod will be given a path in ingress, eg - /vm1, which can be accessed using hostname, eg, www.hostname.com/vm1.
When a new pod is created and ingress rule is added to access the pod, the update to ingress rule should not disrupt the working/availability of the existing pods and
the newly added pod and path should be available for access without any restart.
Acceptance Criteria:
1. Setup digitalocean cluster.
2. Setup traefik proxy.
3. Deploy pods with different resources (cpu, memory, storage) size vms, servies, ingress.
4. Set up dns service.
5. Access and run the vm from pods.
6. When multiple vm are running.
7. Add new pods, services and update ingress with new rules/path.
8. Adding/updating new pods/services/ingress should not disrupt the current running vms.
9. Newly added pods can be accessed without having to restart.
10. Give a demo on above.
11. Setup the whole thing in the given environment.
12. Any errors if occurs should troubleshoot and fix it.