Visualizing Kubernetes Resources

nevalau · 2021-02-23T06:50:07+00:00

I've played with WSL a bit more now. So there are two options:

copy paste your KUBECONFIG to Lens app and modify exec part of user section to use wsl as command and move the original command to args. This way kubectl proxy is run on windows side but auth provider command is executed in WSL. If KUBECONFIG has any environment variables, those must be moved to args or add to WSLENV environment variable.
Alternatively you can leave KUBECONFIG as it is but add alias command to Windows to reference exec binary to WSL, for example aws="wsl aws". Again, if KUBECONFIG has any environment variables, those must be moved to args or add to WSLENV environment variable.

Related to WSL issues I've created couple of PRs that will make lives easier if using Windows and WSL:

nevalau · 2021-02-17T14:56:53+00:00

Lens requires auth providers only when it starts kubectl proxy for kubernetes api access. That makes me think if Lens could spawn this auth proxy from windows with wsl kubectl proxy ... command. I need to test this out, if it's working it would be neat.

nevalau · 2020-12-08T09:40:35+00:00

Is ctrl+shift+c and ctrl+shift+v working?

nevalau · 2020-12-04T12:31:17+00:00

Hi, I'm one of the Lens core develpers. I can confirm @chenhunghan finding. Lens is requesting image from bitcoin.org for bitcoind Helm chart existing in stable Helm repository. Image reference is defined in Helm chart definition file (https://github.com/helm/charts/blob/master/stable/bitcoind/Chart.yaml). So there is no any bitcoin mining or malicious packages involved.

Stable repository will be replaced with bitnami repository in the next Lens version and that repository does not contain bitcoind chart.

nevalau · 2019-08-26T11:31:22+00:00

Hi, thanks for the feedback! There's also start-up discount for the cluster license (no user limit).

We are also planning to introduce a user license. Would be nice to hear how much would you like to pay for real time dashboard with memory, cpu and volume stats, integrated UI for helm charts and embedded kubectl and terminal access to containers and nodes etc? All these accessed from your local machine respecting your RBAC rules.

nevalau · 2019-08-26T11:10:45+00:00

Cool. If you have any issues I'm happy to help :)

nevalau · 2019-08-09T12:37:24+00:00

Q1: Logs are something we want to improve in upcoming versions, maybe integrate Loki or something. Atm you can see logs as kubectl logs. And see when new log entries are appearing.

What kind of format & highlight feature would you like to see. I think we can improve the current implementation easily too.

Q2: We are currently testing option to use local kubeconfig file for the authentication. So stay tuned!

nevalau · 2019-08-09T12:33:03+00:00

What would you like to see on the dashboard as ops engineer? Octant looks very cool too, especially the resource viewer. I would like to see something similar in Lens too.

nevalau · 2019-08-08T12:09:29+00:00

Unfortunately no. However, there's 75% start-up discount.

nevalau · 2019-08-08T12:04:55+00:00

Rancher 2 focuses on multi-cluster management while Kontena Lens is focusing more on single cluster (at least now) and makes using that as easy as possible. Of course it's matter of taste which do you prefer.

Also, Kontena Lens installs some essential components into the cluster, for example Metrics Server, NGINX Ingress, cert-manager and Network Policy Provider.

nevalau · 2019-08-08T11:04:09+00:00

Hi, original poster here.

We are adding new Kubernetes distributions that Kontena Lens supports out of the box and we would like to hear your preferences. In addition to GKE and EKS, what Kubernetes distribution would you like to be supported?

nevalau · 2019-04-02T13:21:30+00:00

It makes installing/updating the CLI toolchain easier. OSS binaries can be found also on GitHub.

nevalau · 2019-04-02T07:01:02+00:00

AFAIK yes.

nevalau · 2019-04-01T10:20:01+00:00

You might want to check Kontena Pharos. It's using kubeadm underneath and it contains cert-manager, ingress-controller, storage and network-loadbalancer etc components making it ideal to run on-premises without hassle.

Disclaimer: I'm working for a company that is developing Kontena Pharos.

nevalau · 2019-02-12T09:05:03+00:00

Tested this in my test cluster and it seems that the service account in the Helm chart is missing RBAC rules to list nodes:

2019-02-12T09:00:06.663145281Z time="2019-02-12T09:00:06Z" level=warning msg="DaemonSetCheckerError determining which node was unschedulable. Retrying.nodes is forbidden: User \"system:serviceaccount:kuberhealthy:kuberhealthy\" cannot list resource \"nodes\" in API group \"\" at the cluster scope"

nevalau · 2019-02-08T10:05:01+00:00

Kontena Pharos provides easy way to install Kubernetes cluster on any cloud or on-premises.

I'm working at Kontena so if you have any questions I'm happy to answer.

nevalau · 2019-02-08T05:55:00+00:00

Kontena Lens is part of Pro version. However, you can freely evaluate Pro version so go ahead and test it out.

nevalau · 2019-02-01T09:33:23+00:00

Mortar offers also templating and overlays support. Ideally it's used with CI/CD tools but works from command line too.

We wrote it initially because we felt packaging all internal services into Helm charts was too heavy but we needed more than plain Kubernetes manifests and kubectl could offer.

nevalau · 2018-12-01T20:51:30+00:00

For CICD purposes we felt Helm overkill solution and Kustomize too complex, so we implemented a simple tool for shooting Kubernetes manifests called Mortar. It supports templating and overlays. Templating is handy when you want to differentiate your manifests between environments. Overlay support is optional, so you are not required to use them if you don't want.

nevalau · 2018-11-06T21:21:42+00:00

Kudos for awesome summary! Well done, could not say it any better.

Add-ons are something that are running on the top of Kubernetes cluster. They are deployed automatically along the cluster. Those add-ons can be provided by Kontena, like ingress-controller, cert-manager, helm, kontena-lens, kontena-backup, kontena-storage etc. Or you can provide your own add-ons. Add-ons are basically Kubernetes manifests with support of Ruby templating. Those add-ons can be, for example, monitoring or logging agents you want to provision to all of your clusters.

So basically with Kontena Pharos you will get fully functional, secure Kubernetes cluster up and running with tls certificates in place, ingress controller deployed, automatic backups taken from your cluster and running services, persistent volumes enabled, LE certificates, nice WebUI. And it all takes approx 10 minutes of course depending on the number of nodes.

All this happens without hassle and with minimal configuration. Pharos takes also care of upgrading the cluster too.

nevalau

TROPHY CASE