Kubernetes: Kubectl is CRAZY simple⚡ yet very few use it effectively. So, here are 7 joyful, less used, kubectl commands that makes your Kubernetes life easy and fun! ☺️ kubectl top node Displays resource utilization (CPU/Memory/Storage) for nodes. Pinpoints potential node bottlenecks. kubectl top pod - Reveals resource utilization (CPU/Memory/Storage) for pods. - Flags potential pod performance issues. kubectl logs POD_NAME [-c CONTAINER_NAME] [flags] - Fetches pod logs. - Aids in pod troubleshooting and real-time insight. kubectl describe RESOURCE_TYPE RESOURCE_NAME [flags] - Offers detailed info on a Kubernetes resource. - Provides a deep dive into resource attributes. kubectl edit RESOURCE_TYPE RESOURCE_NAME [flags] - Opens an editor to modify Kubernetes resource definitions. - Streamlines resource adjustments without recreation. kubectl exec POD_NAME [-c CONTAINER_NAME] — COMMAND - Executes commands within a pod. - Simplifies pod issue diagnostics through command execution. kubectl port-forward POD_NAME LOCAL_PORT:REMOTE_PORT [flags] - Directs a pod's port to your local machine. - Access pod applications from your local device. That's it for today. If this is useful, do a Repost. It really helps ♻ Follow me Mutha Nagavamsi for simplified #Kubernetes , #tech , #devops content. You can find me on Medium. Just search for my name on Google. Before you leave, don't forget to SMILE 😁 Bonus: 🥳 kubectl proxy -p 8001 → This would start a proxy on port 8001 that forwards requests to the Kubernetes API server. → You can then access the API server using the proxy, by making requests to localhost:8001

RBAC is at the heart Kubernetes security ⚡ Without RBAC, anyone can make your cluster a open playground at a party 🎉 Needless to say, your cluster is vulnerable without it. So, to enable RBAC and secure your cluster, you need to first understand the following: Authentication: Verify user identity through various methods like certificates or tokens. Authorization: Decide what actions a user is allowed to perform on resources. Role: Defines access rules for specific resources within a namespace. RoleBinding: Connects roles to users or groups within a namespace. ClusterRole & ClusterRoleBinding: Expands role-based access control to the entire cluster. RBAC is a first step of your K8s security. Embrace it with open arms! 🤗 I will create a practicle video on RBAC very soon. Do checkout my channel. That's all for today. If this is useful, do a Repost. It really helps ♻ Follow me Mutha Nagavamsi for simplified #Kubernetes , #tech , #devops content. You can find me on Medium and X. Just search for my name on Google. Before you leave, don't forget to SMILE 😁