DevOps series “from cloud to ground” – Part 0: Introduction and stories

Starting as a web developer, i do not have any experience in DevOps world. With me and i think with almost all of us DevOps is very complicated and difficult. But luckily I have a  chance to work with it, so I need to learn it. So let see how a zero knowledge devops like me start to learn and deploy things getting a web up and running. This series is a story how i learn devops so i can deploy my applications and also my company’s application. First on the cloud (the aws) then when run out of money we go down to the ground :)))) (host all services in a physical server). I will try to make it as simple as possible so people don’t know anything devops like me can understand.

In this series ?

I will break down my stories into 12 parts like thisMonitoring and debugging with Open Observe and lens

  1. Part 1: My first time deploy a web to a aws cloud service
  2. Part 2: Docker and containerization
  3. Part 3: K8s and the new world of container orchestration
  4. Part 4: Deploy your express application to k8s
  5. Part 5: Networking with K8s is f***ing hard 🙁
  6. Part 6: From the cloud to ground: Physical server setup for a private cloud
  7. Part 7: From the cloud to ground: Install Ubuntu Server and Microk8s
  8. Part 8: From the cloud to ground: Harvester HCI for real world projects
  9. Part 9: From the cloud to ground: Private images registry for our private cloud
  10. Part 10: From the cloud to ground: Accept outside world traffics via Cloudflare tunnel
  11. Part 11: From the cloud to ground: CI/CD with git hub runners
  12. Part 12: Monitoring and debugging with Open Observe and lens

Exclamations

There are a lot of things in the devops world. This series is just going around my solutions, tools I used to complete my tasks. Maybe it is not the best way or the best practice but I think it may be the easiest way and the cheapest way because I’m not rich :v. So let’s go to Part 1: My first time deploy a web to a aws cloud service

Leave a Reply

Your email address will not be published. Required fields are marked *