Configuration from kubeconfig files (KUBECONFIG environment variable or $HOME/.kube)
Switch contexts interactively
<<authentication,Authentication support>> (bearer token, basic auth, private key / cert, OAuth, OpenID Connect, Amazon EKS, Google Kubernetes Engine, Digital Ocean)
Namespace selection and pods list watching
Container log scrolling / watching
Container resources usage (memory, CPU, network, file system charts) footnote:[Requires {uri-cadvisor}[cAdvisor] to be deployed as a DaemonSet. See the <> section for more details.]
Kubebox can be served from a service hosted in your Kubernetes cluster.
Terminal emulation is provided by {uri-xterm-js}[Xterm.js] and the communication with the Kubernetes master API is proxied by the server.
To deploy the server in your Kubernetes cluster, run:
To shut down the server and clean-up resources, run:
$ kubectl delete namespace kubebox
For the Ingress resource to work, the cluster must have an Ingress controller running.
See {uri-ingress-controllers}[Ingress controllers] for more information.
Alternatively, to deploy the server in your OpenShift cluster, run:
You can run Kubebox as an in-cluster client with kubectl, e.g.:
$ kubectl run kubebox -it --rm --env="TERM=xterm" --image=astefanutti/kubebox --restart=Never
If RBAC is enabled, you'll have to use the --serviceaccount option and reference a service account with sufficient permissions.
=== Docker
You can run Kubebox using Docker, e.g.:
$ docker run -it --rm astefanutti/kubebox
You may want to mount your home directory so that Kubebox can rely on the ~/.kube/config file, e.g.:
$ docker run -it --rm -v ~/.kube/:/home/node/.kube/:ro astefanutti/kubebox
=== Online
Kubebox is available online at https://astefanutti.github.com/kubebox.
Note that it requires this address to match the allowed origins for CORS by the API server.
This can be achived with the {uri-kube-apiserver}[Kubernetes API server CLI], e.g.:
$ kube-apiserver --cors-allowed-origins .*
== Authentication
We try to support the various authentication strategies supported by kubectl, in order to provide seamless integration with your local setup. Here are the different authentication strategies we support, depending on how you're using Kubebox:
|OpenID Connect
|{icon-check}
|{icon-check}
|{icon-check}footnote:[Custom IDP certificate authority files are not supported in Web versions.]
|Amazon EKS|
{icon-check}
|
|
|Digital Ocean
|{icon-check}
|
|
|Google Kubernetes Engine|
{icon-check}
|
|
|===
If the mode you're using isn't supported, you can refresh the authentication token/certs manually and update your kubeconfig file accordingly.
== cAdvisor
Kubebox relies on {uri-cadvisor}[cAdvisor] to retrieve the resource usage metrics.
Before version 0.8.0, Kubebox used to access the cAdvisor endpoints, that are embedded in the Kubelet. However, these endpoints are being deprecated, and will eventually be removed, as discussed in https://github.com/kubernetes/kubernetes/issues/68522[kubernetes#68522].
It's recommended to use the provided cadvisor.yaml file, that's tested to work with Kubebox.
However, the DaemonSet example, from the {uri-cadvisor}[cAdvisor] project, should also work just fine.
Note that the cAdvisor containers must run with a privileged security context, so that they can access the container runtime on each node.
You can change the default --storage_duration and --housekeeping_interval options, added to the cAdvisor container arguments declared in the cadvisor.yaml file, to adjust the duration of the storage moving window (default to 5m0s), and the sampling period (default to 10s) respectively.
You may also have to provide the path of your cluster container runtime socket, in case it's not following the usual convention.
|kbd:[Tab], kbd:[Shift+Tab]
|Change focus within the active screen
|kbd:[↑], kbd:[↓]
|Navigate list / form / log
|kbd:[PgUp], kbd:[PgDn]
|Move one page up / down
|kbd:[Enter]
|Select item / submit form
|kbd:[Esc]
|Close modal window / cancel form
|kbd:[Ctrl+z]
|Close current screen
|kbd:[q], kbd:[Ctrl+q]
|Exit footnote:[Not available in Web versions.]
2+^.e|Login
|kbd:[←], kbd:[→]
|Navigate Kube configurations
2+^.e|Pods
|kbd:[Enter]
|Select pod / cycle containers
|kbd:[r]
|Remote shell into container
|kbd:[m]
|Memory usage
|kbd:[c]
|CPU usage
|kbd:[t]
|Network usage
|kbd:[f]
|File system usage
|kbd:[e]
|Pod events
|kbd:[Shift+e]
|Namespace events
|kbd:[Ctrl+e]
|Cluster events
|===
== FAQ
Resources usage metrics are unavailable!
** Starting version 0.8.0, Kubebox expects {uri-cadvisor}[cAdvisor] to be deployed as a DaemonSet. See the <> section for more details;
** The metrics are retrieved from the REST API, of the cAdvisor pod running on the same node as the container for which the metrics are being requested. That REST API is accessed via the API server proxy, which requires proper RBAC permission, e.g.:
+
[source,shell]
Permission to list the cAdvisor pods (selected using the spec.nodeName field selector)
$ kubectl auth can-i list pods -n cadvisor
yes
Permission to proxy the selected cAdvisor pod, to call its REST API
$ kubectl auth can-i get pod --subresource proxy -n cadvisor
yes
The npm package kubebox receives a total of 48,395 weekly downloads. As such, kubebox popularity was classified as popular.
We found that kubebox demonstrated a not healthy version release cadence and project activity because the last version was released a year ago.It has 1 open source maintainer collaborating on the project.
Package last updated on 09 Apr 2022
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Malicious Go packages are impersonating popular libraries to install hidden loader malware on Linux and macOS, targeting developers with obfuscated payloads.
Bybit's $1.46B hack by North Korea's Lazarus Group pushes 2025 crypto losses to $1.6B in just two months, already surpassing all of 2024's $1.49B total.
OpenSSF has published OSPS Baseline, an initiative designed to establish a minimum set of security-related best practices for open source software projects.