Ultimate DevOps Project Implementation

Discover the docker lifecycle for containerizing microservices, including creating a dockerfile, building an image, and running a container with docker build and docker run.

Log in to the EC2 instance via SSH using the PEM file, identify Golang, Java, and Python microservices, build the Go-based product catalog binary with go.mod, and begin Docker containerization.

Containerize a Java add microservice by building locally with the Gradle wrapper, installing dependencies, and producing a bin executable and jar, then export port 999 for testing.

Learn to containerize a Java microservice by building a multi-stage Docker file, manage Gradle dependencies, include a proto file, and optimize the final image.

Containerize a python-based recommendation service by creating a dockerfile, installing dependencies from requirements.txt, and running recommendation_server.py.

Discover how docker init writes dockerfiles for rust and other languages, creates a multi-stage image, and guides you through port choices, builds, and desktop versus ec2 usage.

Push local container images to centralized registries such as Docker Hub, docker.io, or AWS ECR by authenticating with docker login and using docker push to create repositories with tags.

Explore how to start with Kubernetes, compare local vs managed clusters, and deploy a managed cloud Kubernetes cluster with Terraform, including virtual private cloud setup, remote backend, and state locking.

Learn the Terraform lifecycle across init, plan, and apply, including provider and backend initialization, the plan dry-run, and the apply step that creates resources via cloud provider APIs.

Authenticate Terraform with aws by creating iam access keys and configuring the aws cli with aws configure. Terraform reads dot aws credentials file during plan or apply to create resources.

Discover how the terraform state file acts as the heart of terraform's memory, recording resources created by apply and updating with changes to enable safe deletions.

Learn how Terraform state locking uses DynamoDB with a remote backend like S3 to prevent concurrent applies and avoid race conditions.

Learn to create a Terraform backed AWS state store by provisioning an S3 bucket and a DynamoDB table for remote state locking, with provider setup and resource blocks.

Adopt a modular approach in Terraform by creating and invoking reusable VPC and ECS modules, avoiding duplicate code and promoting shared modules via Git repositories.

Design and implement a reusable vpc module with terraform, including vpc, private and public subnets, internet gateway, nat gateway, route tables, and variables and outputs.

Learn to create a VPC and ECS on AWS using Terraform modules with a remote S3 backend and DynamoDB state locking, including plan and apply.

Learn to connect to one or more Kubernetes clusters from the command line by configuring kubeconfig contexts with kubectl and updating kubeconfig via the aws eks update-kubeconfig command.

Learn why every pod needs a service account in Kubernetes, how default accounts work, and how to grant permissions via role bindings or cluster role bindings for api access.

Discover how the deployment resource handles scaling and healing by managing a replica set, and how the service resource enables stable networking on an eks cluster.

Learn how Kubernetes services solve the service discovery problem by using a proxy with labels and selectors instead of IP addresses, enabling front-end to reach back-end pods via service name.

Explore Kubernetes service manifests, including api version v1 and kind service, configure metadata, labels, selectors, ports, and target ports, and understand FQDNs for internal and external access.

Deploy and validate a multi-service Kubernetes project by applying merged deployment and service YAMLs, creating a service account, and verifying pods and services before planning external access.

Expose the app on Kubernetes by changing the frontend service to a load balancer, wait for the fqdn, and verify the end-to-end shopping flow from cart to order.

examine the drawbacks of load balancer service type, including non-declarative provisioning and higher costs, and compare it to the declarative, cost-efficient, and flexible ingress approach.

Install alb ingress controller on the ECS cluster and configure IAM OIDC provider with a mapped service account and IAM role, using a downloaded policy and helm deployment.

Access the front end proxy via an ingress resource, configure host and path routing to example.com, and verify load balancer provisioning and ingress controller operation.

Learn how to obtain a real custom domain, connect it to your Kubernetes ingress load balancer, and map DNS with providers like GoDaddy to access your project.

Create a public hosted zone in Route 53, configure a www alias record to your load balancer, and update GoDaddy name servers to route ownership to Route 53.

Map your custom domain by creating a Route 53 hosted zone and updating GoDaddy name servers, then verify DNS propagation with what's my DNS, NS lookup, and curl --resolve.

Update the ingress host name to match the Route 53 alias, apply the ingress configuration, and wait for the ingress controller to propagate the changes to access the custom domain.