If you are planning to use this repo for reference, please hit the star. Thanks!
🚀 CKA, CKAD, CKS, or KCNA exam aspirants can save $60 today using code DCUBEOFFER at https://kube.promo/devops. It is a limited-time offer from Linux Foundation.
- Learn Container concepts & Gets Hands on with Docker Complete Guide
- Understand Distributed system Blog
- Understand Authentication & Authorization Blog
- Learn Basics of Key Value StoreBlog
- Learn the basics of REST APIBlog
- Learn YAMLBlog
- Understand Service Discovery Blog
- Learn Networking Basics
- L4 & L7 Layers (OSI Layers)Blog
- SSL/TLSBlog
- Network Proxy BasicsBlog
- DNSBlog
- IPTablesVideo
- Software Defined Networking (SDN)Blog
The Following image shows the high level kubernetes architecture and how external services connect to the cluster.
Refer the follwing documents to learn the Kubernetes Architecture.
As DevOps engineers, gaining a thorough understanding of each component and cluster configuration is crucial to work in production environments. Though there are various methods for deploying a Kubernetes cluster, it is advisable to learn how to set up multi-node clusters from scratch. This allows you to gain knowledge on concepts such as High Availability, Scaling, and Networking, and simulates a real-world project.
Additionally, mastering the configuration of multi-node clusters can be beneficial for interviews and building confidence in your abilities. The following are recommended ways to establish a Kubernetes cluster.
- Kubernetes the Hard WayGithub
- Kubeadm Cluster SetupBlog
- Minikube Development Cluster Blog
- Kind Development ClusterOfficial Documentation
- Vagrant Automated ClusterGithub
Launching large clusters in the cloud can be costly. So utilize the available cloud credits to practice deploying clusters as if you work on a real project. All cloud platforms offer managed Kubernetes services.
- GKE -Google Cloud $300 free creditsCloud Platform
- EKS - AWS $300 free POC creditsCloud Platform
- DO Kubernetes - Digital Ocean – $200 free creditsCloud Platform
- Linode Kubernetes Engine - Linode Cloud – $100 Free creditsCloud Platform
- Vultr Kubernetes Engine - Vultr Cloud - $250 Free CreditsCloud Platform
As a DevOps engineer, it is important to become familiar with the Kubeconfig file. It is crucial for tasks such as setting up cluster authentication for CI/CD systems, providing cluster access to developers, and more.
A Kubeconfig file is a YAML file that stores information and credentials for connecting to a Kubernetes cluster. It is used by command-line tools such as kubectl and other client libraries to authenticate with the cluster and interact with its resources.
The Kubeconfig file can be used to store information for multiple clusters and users, allowing users to switch between different clusters and contexts easily. It is an important tool for managing access to and interacting with Kubernetes clusters.
Refer the follwing document to learn about Kubeconfig File in detail.
In Kubernetes, an object is a persisted entity in the cluster that represents a desired state of the system. It is created and managed by the Kubernetes API server, and is stored in the etcd key-value store. Examples of Kubernetes objects include pods, services, and deployments.
Here is an example of a Pod Object
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:
- name: nginx
image: nginx:1.14.2
ports:
- containerPort: 80
A resource is a representation of a Kubernetes object that is exposed by the Kubernetes API. It is a way for clients to interact with and manipulate objects in the cluster.
A resource refers to a specific API URL used to access an object. Resources are typically accessed through the Kubernetes API using HTTP verbs such as GET, POST, and DELETE. For instance, the /api/v1/pods resource can be used to retrieve a list of v1 Pod objects. Additionally, an individual v1 Pod object can be obtained from the /api/v1/namespaces//pods/ resource
<--In Progress-->
<--In Progress-->
<--In Progress-->
<--In Progress-->
<--In Progress-->
<--In Progress-->
<--In Progress-->
<--In Progress-->
- Production Readiness Checklist
- Learn About 12 Factor Apps Official Guide
- Learn From Kubernetes Failure Stories List of Blogs
- Scheduling 300,000 Kubernetes Pods in Production Daily Video
If you do not have real world Kubernetes experience, it is better to read case studies of other companies using kubernetes.
- List of Kubernetes User Case StudiesOfficial Case Studies
- How OpenAI Scaled Kubernetes to 7,500 NodesBlog
- Testing 500 Pods Per NodeBlog
- Dynamic Kubernetes Cluster Scaling at AirbnbBlog
- Scaling 100 to 10,000 pods on Amazon EKSBlog
Helm and Kustomize are both tools that are used to manage Kubernetes manifests. They are similar in many ways, but have some key differences.
Helm is a package manager for Kubernetes that allows users to easily install, manage, and upgrade applications on a Kubernetes cluster. It uses a concept called "charts" which are pre-configured sets of Kubernetes resources that can be easily deployed, upgraded, and rolled back.
Kustomize, on the other hand, is a tool that allows users to customize and configure existing Kubernetes manifests. It uses a concept called "patches" which can be applied to existing manifests to customize them for different environments and use cases. Unlike Helm, Kustomize does not include built-in support for versioning and rollback, and does not have a concept of "packages" or "repositories".
- Learn to Create Helm Chart From ScratchHands-On Blog
GitOps is a approach to Continuous Deployment that uses Git as a single source of truth for declarative infrastructure and application code. Some popular GitOps based tools for deploying applications to Kubernetes clusters are:
-
Argo CDOfficial Doc
-
Argo Rollouts Official Doc
<--In Progress-->