31Days of EKS.

1. Introduction.

2. Things will be covered.

3. Why 31 days of EKS?

   ---

1-Introduction

Hi, there,
Being a DevOps Engineer is not that easy at all, You have to deal with N numbers of tools and technologies to make a tremendously scalable product.

If you are in the same domain you already know that Kubernetes is the most used tool in the cloud, for instance, Snap uses the same and manages 2 million+ transactions a second.

2-Things will be covered

1. CLI Installations(AWS,kubectl,eksctl).
2. Creating EKS Cluster.
3. NodeGroups, IAM OIDC Provider.
4. Kubernetes Basic commands.
5. EKS Storage, Volume, VPC, etc.
6. EKS Private Node groups. 
7. Ingress, Loadbalancer(ALB,NLB,CLB).
8. IAM, Kubernetes service accounts, RBAC.
9. HELM Deployments
10. SSL,CPR, External DNS.
11. And much more...

3-Why 31 days of EKS?

MicroServices are already gaining popularity in the Software industry, and more and more software developers now like to work in docker container-based development environments.

EKS is the widely used mature method for the deployment of microservices. Knowing How EKS works are much helpful in your daily deployment needs.

If you are planning to use microservices in your upcoming container project, the benefits are worth considering.

Let me know if you have any questions!
Thanks.