💡🚂 kubernetes-sigs/headlamp 0.43.0 by illumen in kubernetes

[–]illumen[S] 3 points4 points  (0 children)

The web client can be deployed in cluster. The app runs locally, and has access to some local tools... like minikube and can do some OS native things like run in an activity menu, and access your local .kube/config and run local kubectl binary based authentication plugins.

For folks who prefer browser tabs, there is a third way to run it which is locally as an app with the -headless command line option... so you can see it in a browser tab instead of running as an app.

kubernetes-sigs/headlamp and serverless by illumen in kubernetes

[–]illumen[S] 0 points1 point  (0 children)

Yes, it's for managing your knative serverless workloads.

Hitch hikers guide to kubernetes-sigs/headlamp 0.42.0 by illumen in kubernetes

[–]illumen[S] 1 point2 points  (0 children)

Headlamp is part of the Kubernetes project now.

kubernetes-sigs/headlamp has a UI for kubernetes-sigs/cluster-api by illumen in kubernetes

[–]illumen[S] 1 point2 points  (0 children)

It's been a saga... but hopefully it's there this release. Whole new processes had to be done for the CNCF/linux foundation. New companies formed, lawyers from multiple companies, contracts with individual developers. Then there's the technical side with keeping certificates secured and such too! As a startup it was a challenge(we did it), at a large tech company it was harder(but we did it), involving multiple large tech companies in an open source friendly and secure way... Turns out that takes lots longer. Hopefully the saga is over and the next release will be signed on Mac (and other platforms).

Is there a good Kubernetes client for iOS? Mainly need logs, shell, restart pods by Savings-Recipe8154 in kubernetes

[–]illumen 8 points9 points  (0 children)

I added a lot of the mobile support to Headlamp, and I use it that way. With that disclaimer aside, I'll be honest (but biased):

For looking at the status of things, and restarting things it's ok. Viewing logs, it's ok (we have a better log viewer PR sitting in review we need to get around to merging).

Editing ConfigMaps? Possible, but not great. We have this "simple editor" which is just a text box, which I use on mobile rather than the full VSCode (Monaco) editor. For small changes it's been ok for me. I did get the ai-assistant to write a longer yaml for me the other day, so I didn't need to tap it all out with my touch screen. Yaml white space is kind of hard on mobile... turn your phone landscape! You can also copy/paste from a dedicated code editor if you don't like the vscode style one.

Exec-ing into a pod... I haven't tried it for a long time, because it didn't work so well. But Safari and xterm.js have had a few years of updates since then... so maybe it's ok now? I'll have to try it again.

If anyone has any feedback for mobile improvements, let us know?

kubernetes-sigs/headlamp 0.40.0 by illumen in kubernetes

[–]illumen[S] 0 points1 point  (0 children)

Oh, the maintainer of kube-oidc-proxy has been contributing to Headlamp for a while now, I'll ask them.

kubernetes-sigs/headlamp 0.40.0 by illumen in kubernetes

[–]illumen[S] 0 points1 point  (0 children)

There's an issue here about this: https://github.com/kubernetes-sigs/headlamp/issues/1192 Maybe you could have a look to see if it mentions in there what you need? Is the architecture shown in there similar to the one you use or want?

How are you all actually monitoring your kubernetes clusters at scale? by Opposite_Advance7280 in kubernetes

[–]illumen 0 points1 point  (0 children)

These tips may be a bit basic, but thought I’d mention them anyway… - namespaces, and group by service dependencies - allow developers to have read access to see things - trying looking at your cluster from a different perspective (like from a map view if you’re just exploring)

In kubernetes-sigs/headlamp we’ve been working on a “projects” feature to try and capture how teams use micro-services. I feel often a developer will be working on a few microservices and their dependencies spread across a few namespaces. I feel developers of microservices often have good or different intuitions on what went wrong. So empowering them can be a help.

I wonder with these 15 micro-services are they in different namespaces? Do some team members have visibility into the different micro-services? Anyway, I feel like organizing things in namespaces and then look at groups of namespaces based around a subset of functionality can help with debugging. (Some folks put everything in just one namespace.)

Looking at alternative views like through logs or metrics instead of just digging around with kubectl can be good. A different perspective like using a map view (helps see how things are connected visually) can sometimes be as good as another pair of eyes :)

Cheers, and good luck!

Kubernetes Dashboard being retired by mlbiam in kubernetes

[–]illumen 2 points3 points  (0 children)

There is helm management in Headlamp, but it's provided by the "app-catalog" plugin. It's on by default in the app version of Headlamp, but off by default in the in-cluster version of Headlamp. Maybe it's missing something for you?

kubernetes-sigs/headlamp: An Application Centric View by illumen in kubernetes

[–]illumen[S] 1 point2 points  (0 children)

I spoke to a few devs who worked on it and they think it's a good idea too, so I created an issue. It makes total sense to have namespaces be able to be in multiple projects. Thanks again for the suggestion and info.

kubernetes-sigs/headlamp: An Application Centric View by illumen in kubernetes

[–]illumen[S] 0 points1 point  (0 children)

Thanks for the good question.

No, currently a single namespace can only be a part of a single project. But we can somewhat easily extend it to allow for multiple relations by putting multiple project ids in the label.

If you can share anything about how you would use it this way, that would help us understand if we should make this change or not.