KB:Kubernetes run imperative Busybox pod and connect

#buysbox
kubectl run -it --rm busybox01 --image=busybox --restart=Never --command -- sh

#Network Tools
kubectl run -it --rm netshoot --image=nicolaka/netshoot --restart=Never --command -- bash


note, busybox image uses "sh" shell, /bin/bash will not work!
by design busybox will exit, there is no process/cmd that will run, so you have to connect to the pod/container during run time by overriding the command arg. 

  • kubectl run: This is the command used to create and run a new Pod.

  • -it: This flag is a combination of -i and -t. -i stands for "interactive", which keeps the stdin open even if not attached, and -t stands for "tty", which allocates a TTY (terminal).

  • --rm: This flag tells Kubernetes to automatically remove the Pod once it has finished executing.

  • busybox01: This is the name of the Pod being created.

  • --image=busybox: This specifies the Docker image to use for the Pod. In this case, it is the busybox image, which is a lightweight Linux distribution.

  • --restart=Never: This specifies the restart policy for the Pod. By setting it to Never, Kubernetes will not attempt to restart the Pod if it exits.

  • --command: This flag indicates that the following arguments should be treated as the command to run in the container.

  • -- sh: This specifies the command to run inside the container. sh is the shell command, which will start a shell session inside the container.

In summary, this command runs a temporary interactive BusyBox container with a shell (sh), and the Pod will be deleted automatically after the shell session ends. This is useful for running one-off tasks or debugging purposes in a Kubernetes cluster.


Ref: https://hub.docker.com/_/busybox


Comments

Post a Comment

Popular posts from this blog

KB: Azure ACA Container fails to start (no User Assigned or Delegated Managed Identity found for specified ClientId)

Image
When deploying secure workloads using Azure Container Apps (ACA) , teams often face confusion between User Assigned Managed Identities (UAMI) and App Registrations . While both entities are visible in Azure Active Directory and have similar identifiers (Application ID, Object ID), they serve very different purposes . This confusion can lead to authentication failures when accessing services like Azure App Configuration or Key Vault . A common issue occurs when a container app is configured with a managed identity, but the environment variables or role assignments mistakenly reference an App Registration instead, causing errors like: "No User Assigned or Delegated Managed Identity found for specified ClientId" This article breaks down the difference between UAMI and App Registrations, explains why this issue happens, and outlines the correct approach to resolve it. Symptoms Azure Container App fails to authenticate to Azure App Configuration or other services. Logs...
Read more

Electron Process Execution Failure with FSLogix

  Technical Note: Electron Process Execution Failure with FSLogix 1. Overview When running Electron-based applications in environments using FSLogix Profile or Office Containers , users may encounter issues where the Electron process fails to launch or execute properly . This behavior has been observed in Azure Virtual Desktop (AVD) , Windows Virtual Desktop (WVD) , and other environments where FSLogix filter drivers are active. 2. Symptoms Electron-based applications (e.g., desktop apps built on Electron, CLI wrappers) do not start , remain unresponsive, or terminate silently. No visible logs or error messages are generated by the application. Standard executables run correctly when placed outside of the FSLogix-controlled profile path (e.g., copying to C:\Temp allows execution). The issue is reproducible across all Electron apps in the FSLogix-managed profile. 3. Root Cause The issue is linked to FSLogix filter drivers ( frxdrv , frxdrvvt , frxccd ) interfe...
Read more

KB:RMM VS DEX (Remote Monitoring Management vs Digital Employee Experience)

Digital Employee Experience (DEX) and Remote Monitoring and Management (RMM) tools serve different purposes and cater to distinct aspects of IT and employee management. Digital Employee Experience (DEX) Focus: Enhancing the overall experience of employees with their digital workplace tools and environment. Key Features: User Experience Monitoring: Tracks how employees interact with software and hardware, identifying issues impacting productivity. Performance Analytics: Provides insights into the performance of applications from the end-user's perspective. Feedback Mechanisms: Allows employees to report issues and give feedback on their digital tools and environment. Employee Well-being: Monitors factors that affect employee satisfaction and well-being, such as system performance and usability. Proactive Support: Identifies potential issues before they become significant problems, enabling proactive IT support. Goals: Improve employee satisfaction and productivity. Ensure a sm...
Read more