Hello everyone, It’s my pleasure to announce the v0.1.0 release of the Kubectl EKS Plugin. I had this of the kubectl plugin for EKS from the day I started using Amazon EKS. But I finally made it into reality and cut the first release. The mission of the kubectl EKS plugin is to simplify operations and provide easy access to cluster-related information. The first release of kubectl-eks has few but convenient functionalities. I am excited about this project and hope to see more features in the upcoming months. ...

Sometimes, When IAM user tries to register a new Virtual MFA device using Google Authenticator or similar tools, they notice the following error, Entity Already exists This entity already exists. MFADevice entity at the same path and name already exists. Before adding a new virtual MFA device, ask your administrator to delete the existing device using the CLI or API. This happens because the MFA device was created but not enabled for the users. It may happen because of various reasons. If you are a system administrator or platform engineer, this can be little pain to figure out the issue. ...

I regularly use *terraform plan -no-color* command to check the plan in a more readable way. I wrote a blog post regarding the same here. Give it a read if you haven’t already. Running this command every time is quite cumbersome. Hence I was looking for options and came across these terraform environment variables features. I can export TF_CLI_ARGS as shown below with the arg. export TF_CLI_ARGS="-no-color" Now, If I run terraform plan it will be equivalent of terraform plan -no-color ...

A few days ago, I was working on an application which consisted of a multi-container pod where I had to send a signal from container A to a process from container B within the same Pod. We know containers inside the pod already share the network namespace by default which means they technically have the same IP address. Apart from this, most things, such as other namespaces, are isolated. For example, process namespace. Containers within the same pod run their process namespace and don’t share any information with another container. ...

Often we find it difficult to visualize the Kubernetes secrets as they are base64 encoded. You will need to manually copy the encoded data and then decode it or write small custom shell scripts for the same. Fortunately, there’s a kubectl plugin to simplify this process. view-secret The plugin allows users to view the contents of a secret without having to decode it manually. Check out the project on GitHub: ...

Have you ever wondered about running kubectl commands in parallel for some of your clusters? You must have written custom shell scripts or Golang scripts to do so. Fortunately, a tool to run commands in parallel now exists, Thanks to Ahmet Alp Balkan 🙏 Check out the GitHub repo, and don’t forget to ⭐️ the repo :) https://github.com/ahmetb/kubectl-foreach kubectl-foreach Is a tool that allows users to run a kubectl command in one or more contexts (clusters) in parallel. This can be very useful when you need to perform an action on all of the resources in given contexts/clusters, such as gathering information, scaling them up or down, rolling out an update, or applying a configuration change. ...

Kubernetes and Terraform are both powerful tools for managing cloud infrastructure, but they use different configuration languages. Kubernetes uses YAML, while Terraform uses HashiCorp Configuration Language (HCL). This can make it difficult to use the two tools together, as you may need to convert YAML files to HCL in order to use them with Terraform. Sometimes when you are spinning up managed Kubernetes such as GKE, EKS and AKS, you may need to deploy Kubernetes resources via terraform. ...

When we work around Kubernetes, we often have to reference the documentation for a few things to save time from the journey from terminal to browser and back. Kubectl offers a great set of help in itself. Learning about the resources The command shows all fields from the pod resource along with its type and information about it. You can also look for a subfield. for example, $ kubectl explain pod $ kubectl explain pod.spec.containers ...

Source: https://unsplash.com/photos/pZld9PiPDno When associating IAM roles with pods instead of assigning a super role to worker nodes, Kiam is a fairly popular project in Community; kiam runs as an agent on each node in the Kubernetes cluster, allowing cluster users to associate IAM roles to Pods. To enhance security, Kiam uses certificates for servers & agents. To simplify the certificate management for Kiam, we will utilise cert-manager, cert-manager is a native Kubernetes certificate management controller that helps issue certificates from various sources or self-signed ones. ...

Last week, while going through some of the Kubernetes manifest files, I stumbled upon this label: kubernetes.io/cluster-service: “true” I searched about this in Documentation but could not find much information, so I thought of writing a small blog post about it. https://surajincloud.gumroad.com/l/own-kubectl-command When you add this label to any resource of type Kind: Service , it means it is part of cluster service, and the user needs to know when they are looking for cluster information. Hence it appears in the following command: ...