DevOps & Cloud (AWS, AZURE, GCP) Tech Free Learning

🛡 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗣𝗼𝗱 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗔𝗱𝗺𝗶𝘀𝘀𝗶𝗼𝗻 🛡 ➡️ Within Kubernetes, containerized applications are managed as logical units called 𝐏𝐨𝐝𝐬. In any deployment environment, these 𝐏𝐨𝐝𝐬' security is vital. Kubernetes provides various security controls, such as 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐒𝐭𝐚𝐧𝐝𝐚𝐫𝐝𝐬 (𝐏𝐒𝐒) and 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 (𝐏𝐒𝐀), to efficiently manage the permissions and capabilities of Pods. These controls ensure that Pods operate with the minimum required access. This approach minimizes the risk of a compromised Pod affecting other resources. [ 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐯𝐞𝐫𝐬𝐢𝐨𝐧 𝐯𝟏.𝟐𝟏 𝐬𝐡𝐢𝐟𝐭𝐞𝐝 𝐟𝐫𝐨𝐦 𝐏𝐨𝐝𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲𝐏𝐨𝐥𝐢𝐜𝐲 𝐭𝐨 𝐭𝐡𝐞 𝐧𝐞𝐰 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 𝐜𝐨𝐧𝐭𝐫𝐨𝐥𝐬 ] ➡️ While 𝐏𝐨𝐝𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲𝐏𝐨𝐥𝐢𝐜𝐲 served its purpose, the new controls offer a more streamlined and accessible approach to enforcing security policies on Pods. 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 introduces predefined security contexts and customization capabilities, enhancing flexibility, control, and ease of use.Understanding the significance of Pod security is fundamental to managing and operating Kubernetes clusters effectively and securely. ➡️ 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗣𝗼𝗱 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗔𝗱𝗺𝗶𝘀𝘀𝗶𝗼𝗻 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 is a feature introduced in Kubernetes to enforce clear and consistent isolation levels for Pods. It builds upon the Kubernetes Pod Security Standards, guidelines that govern how Pods behave and interact with other resources. By applying security restrictions at the Kubernetes namespace level when Pods are created, 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 provides a mechanism to ensure that Pods operate with only the necessary permissions. This enhances security and aligns with broader best practices in software deployment, minimizing the risk of unauthorized access or compromised resources. The importance of 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 lies in its ability to make security a fundamental and integral part of the Kubernetes ecosystem. Rather than treating security as an afterthought, 𝐏𝐨𝐝 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐀𝐝𝐦𝐢𝐬𝐬𝐢𝐨𝐧 ensures that it is part of the design and operation of every Pod. ➡️ 𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗣𝗼𝗱 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗔𝗱𝗺𝗶𝘀𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝘁𝗵𝗲 𝗱𝗲𝗽𝗿𝗲𝗰𝗮𝘁𝗲𝗱 𝗣𝗼𝗱𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆𝗣𝗼𝗹𝗶𝗰𝘆 Kubernetes version 1.21 significantly shifted from PodSecurityPolicy (PSP) to Pod Security Admission. While PSP intended to enforce security settings on Pods, it was deprecated due to its complexity and lack of flexibility. Pod Security Admission introduces a more streamlined approach, utilizing labels to define admission control modes at the namespace level. These labels dictate the action the control plane takes if a potential violation is detected, such as rejection (enforce), audit annotation (audit), or user-facing warning (warn). 😎 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

📌 https://prodevopsguy.xyz/posts/devops/linux_commands_for_devops_engineer/ ✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

✨ Basic Linux Most used commands for DevOps Engineer 🌟 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

➡️ Understanding Container Runtimes in Kubernetes 👈 A container runtime in Kubernetes is the software component responsible for managing the lifecycle of individual containers within a pod. It's the engine that executes the commands and manages the processes within the container environment. ➡️ What it does: ➡️Creates and starts containers: Based on instructions from the kubelet (the Kubernetes agent on each node), the container runtime pulls the container image, sets up the necessary resources, and fires up the container process. ➡️Manages container resources: It allocates CPU, memory, and other resources as specified in the pod definition, ensuring each container gets its fair share. ➡️Monitors and manages container health: It keeps an eye on the container's health and restarts it if it crashes or becomes unresponsive. ➡️Stops and removes containers: When a container is no longer needed, the runtime gracefully stops it and cleans up its resources. ➡️ Why it's important: ➡️Isolation: Container runtimes create isolated environments for each container, ensuring applications don't interfere with each other or the host system. ➡️Security: They enforce security policies and resource limitations, providing a more secure environment for containerized applications. ➡️Portability: Container runtimes adhere to industry standards, allowing containers to be easily moved between different platforms and cloud providers. ➡️Common container runtimes in Kubernetes. - containerd - CRI-O - Docker Engine - Mirantis Container Runtime ✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

🔥 Understanding Kubernetes Logs - A Comprehensive Guide 🔣 Kubernetes logs are your essential toolkit for spotting and solving container app issues ➡️ Without that valuable insight, you'd be navigating in the dark, risking prolonged downtime and frustrated users. 😎 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

In Kubernetes, readiness and liveness probes are mechanisms used to ensure that applications running inside containers are healthy and able to handle traffic properly. They are essential for maintaining the reliability and availability of applications in a Kubernetes cluster. 📢 Readiness Probe: 🎤 The readiness probe is used to determine when a container is ready to start accepting traffic. It is crucial for ensuring that services don't send requests to a container until it's ready to handle them effectively. 🎤If the readiness probe fails (returns a non-successful HTTP status code or times out), Kubernetes marks the container as not ready, and it won't receive any traffic until the probe succeeds. 🎤The readiness probe can be configured to use HTTP endpoints, TCP sockets, or custom scripts to determine the readiness of the container. 📢 Liveness Probe: 🎤The liveness probe is used to check if a container is still running properly. It helps Kubernetes determine whether a container should be restarted if it's unresponsive or in a failed state. 🎤Unlike the readiness probe, which determines if the container is ready to serve traffic, the liveness probe checks if the container is still functioning correctly after it has started. 🎤If the liveness probe fails (returns a non-successful HTTP status code or times out), Kubernetes restarts the container to try to recover it. ⚠️ Both the readiness and liveness probes are configured to perform an HTTP GET request to the /healthz endpoint on port 8080 of the container.

➡️The readiness probe will start 5 seconds after the container starts and will be performed every 10 seconds thereafter.

➡️The liveness probe will start 10 seconds after the container starts and will be performed every 15 seconds thereafter.

😎 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

👍 Multi-Stage Build Images used in CICD ♾ ➡️ Every microservice should be its own separate container. If you only use a single-stage Docker build, you’re probably missing out on some powerful features of the build process. On the other hand, a multi-stage Docker build has many advantages over a single-stage build for deploying microservices. ➡️ Some Advantages are : - Optimizes the overall size of the Docker image - Removes the burden of creating multiple Dockerfiles for different stages - Easy to debug a particular build stage - Able to use the previous stage as a new stage in the new environment - Ability to use the cached image to make the overall process quicker - Reduces the risk of vulnerabilities found as the image size becomes smaller with multi-stage builds 😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

To ace your 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬 for a DevOps Engineer role ,following Linux related Hardware commands, Data information, Process mgmt., files mgmt, search patterns and packages commands you should be aware of: 𝟏: 𝐇𝐀𝐑𝐃𝐖𝐀𝐑𝐄 𝐈𝐍𝐅𝐎𝐑𝐌𝐀𝐓𝐈𝐎𝐍: -cat /proc/cpuinfo # Display CPU information -cat /proc/meminfo # Display memory information -free -h # Display free and used memory ( -hfor human readable, -mfor MB, -gfor GB.) -lspci -tv # Display PCI devices -lsusb -tv # Display USB devices -dmidecode # Display DMI/SMBIOS (hardware info) from the BIOS -hdparm -i /dev/sda # Show info about disk sda -hdparm -tT /dev/sda # Perform a read speed test on disk sda 𝟐. 𝐌𝐀𝐍𝐈𝐏𝐔𝐋𝐀𝐓𝐈𝐍𝐆 𝐃𝐀𝐓𝐀 : -awk # Pattern scanning and processing language -perl # Data manipulation language -cmp # Compare the contents of two files -paste # Merge file data -sed # Stream text editor -cut # Cut out selected fields of each line of a file -sort # Sort file data -diff # Differential file comparator -split # Split file into smaller files -expand, unexpand # Expand tabs to spaces, and vice versa 𝟑. 𝐏𝐑𝐎𝐂𝐄𝐒𝐒 𝐌𝐀𝐍𝐀𝐆𝐄𝐌𝐄𝐍𝐓: ps # Display your currently running processes ps -ef # Display all the currently running processes on the system. ps -ef | grep processname # Display process information for processname top # Display and manage the top processes htop # Interactive process viewer (top alternative) kill pid # Kill process with process ID of pid killall processname # Kill all processes named processname program & # Start programin the background bg # Display stopped or background jobs fg # Brings the most recent background job to foreground fg n # Brings job nto the foreground 𝟒. 𝐀𝐑𝐂𝐇𝐈𝐕𝐄𝐒 (𝐓𝐀𝐑 𝐅𝐈𝐋𝐄𝐒) : -tar cf archive.tar directory # Create tar named archive .tar containing dir. -tar xf archive.tar # Extract the contents from archive.tar. tar czf -archive.tar.gz director # Create a gzip compressed tar file name archive.tar -tar xzf archive.tar.gz # Extract a gzip compressed tar file. -tar cjf archive.tar.bz2 directory # Create a tar file with bzip2 compression -tar xjf archive.tar.bz2 # Extract a bzip2 compressed tar file. 𝟓. 𝐈𝐍𝐒𝐓𝐀𝐋𝐋𝐈𝐍𝐆 𝐏𝐀𝐂𝐊𝐀𝐆𝐄𝐒: yum search keyword # Search for a package by keyword. yum install package # Install package. yum info package # Display desc and summary information about package. rpm -i package.rpm # Install package from local file named package.rpm yum remove package # Remove/uninstall package tar zxvf sourcecode.tar.gz # Install software from source code. 𝟔. 𝐒𝐄𝐀𝐑𝐂𝐇 : grep pattern file # Search for pattern in file grep -r pattern directory # Search recursively for patternin directory locate name # Find files and directories by name find /home/john -name 'prefix*' # Find files in /home/john that start with "prefix". find /home -size +100M # Find files larger than 100MB in /home 😎 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

☁️ 𝗔𝗪𝗦 𝗵𝗮𝘀 𝗼𝘃𝗲𝗿 𝟮𝟬𝟬 𝗳𝘂𝗹𝗹𝘆 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝗱 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀.✨ 𝗠𝗼𝘀𝘁 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗔𝗪𝗦 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝘆𝗼𝘂 𝘀𝗵𝗼𝘂𝗹𝗱 𝗹𝗲𝗮𝗿𝗻 𝘁𝗼 𝗯𝗲 𝗮 𝗗𝗲𝘃𝗢𝗽𝘀 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿. ✔️Amazon EC2 ✔️AWS IAM ✔️AWS CloudFormation ✔️AWS CloudWatch ✔️AWS CodePipeline ✔️AWS CodeBuild ✔️AWS CodeDeploy ✔️Amazon ECS ✔️AWS Lambda ✔️AWS Elastic Beanstalk ✔️Amazon DynamoDB 😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🔥 AWS DEVOPS REAL-TIME DEPLOYMENT ✨ Development → Pre-PROD → Production ⏰ 🔗 Detailed Project Explanation with Screenshots : https://harshhaa.hashnode.dev/aws-devops-real-time-deployment-dev-pre-prod-production 🔗Project Source code: https://github.com/NotHarshhaa/AWS-DevOps_Real-Time_Deployment 🎄 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

🔔 DevOps AWS (Freshers) Job opportunity ➡️Job Title: DevOps AWS (Freshers) ➡️Location: Hyderabad ➡️Company: RJAY technologies Pvt Ltd ➡️Job Type: Full-time ➡️Job Description:

We are seeking a highly motivated and enthusiastic individual to join our team as an AWS DevOps Engineer.

➡️ Required Skills:

AWS, Docker, kubernetes, Ansible,Linux,Shells Scripting, Python, Jenkins, CI/CD, Git/GitHub

✉️ To apply, please submit your resume to sreeja.k@rjaytechnologies.com ✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🌐 GitOps Workflow - Simplified Visual Guide ➡️ GitOps brought a shift in how software and infrastructure are managed with Git as the central hub for managing and automating the entire lifecycle of applications and infrastructure. ➡️ It's built on the principles of version control, collaboration, and continuous integration and deployment (CI/CD). ✔️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs