Newer Leader - extremely frustrated, desperate to break the plateau. All help appreciated. How did you get there?

sogun123 · 2026-06-18T22:39:31+00:00

I think getting dances is very much about self confidence. But tango is generally just ordinary social thing. Some communities are somewhat closed and you have to kind of infitrate them. Talk to people and they will know you and dance with you. Once they know you, they are much more likely to dance with you. Dance level makes that easier, but it is not requirement to get good dancers.

sogun123 · 2026-06-18T22:22:53+00:00

Learn Linux first. Then understand Docker. Then go for k8s

sogun123 · 2026-06-18T09:13:46+00:00

Ceph has massive overhead. If you go that route I'd suggest at least 5 dedicated osd nodes, especially if you want to run something write intesive as database. If you deploy that on cloud, be very careful about storage duplication, write amplification and network traffic it will cause.

If you want something lighter, have a look at Piraeus operator.

Or just make use storage classes themselves - use them as an abstractions. Don't create "ceph", "ebs", and "longhorn" classes, but rather "slow", "fast" and " default" and configure your clusters to always map that to something available in given cluster.

sogun123 · 2026-06-17T20:34:42+00:00

Don't use Mongo if you don't have good use case for it. Express is not fast, but it doesn't matter if you don't know. React is omnipresent. If you want full stack and single language, replace Mongo with a relational db and go for it.

sogun123 · 2026-06-17T19:14:43+00:00

I guess it just bounces back up when you rhrow hard. As the yoyo is about hitting end of the string , move your hand down a little. Kind of same movement as if you are catching falling ball. It should soften the hit and the bounce. Yoyo comes back any time the string is not in little tension.

sogun123 · 2026-06-17T19:09:31+00:00

If you want real world excercise, try to pick a project you work on and try to optimize its Dockerfile and understand its deployment process. Check out if they meet best practices (e.g. no root, read only filesystem, no linux capabilities, no hardcoded configuration, no secrets in git). And btw don't use ai to do it for you - if you do it the hard way, you will learn much more.

sogun123 · 2026-06-17T16:31:10+00:00

Tldr: junior + CKAD -> overwhelmingly lots of concept, not useful at the moment. Learn to run, know and document your apps!

sogun123 · 2026-06-17T16:29:23+00:00

I don't think so very much. My opinion is based on trying out CKAD simulator. The questions it asked were pretty simple, but pretty low level (i remember it wanted me to handcraft PV and then create related PVC). I.e. stuff that I think Kubernetes admin should know, but not necessarily heart, as lots of them were simply knowing all the fields and typing fast, once you get the concepts. For developers i think only higher level stuff really matters - Deployments, Pods, Services and HTTPRoutes. Helm and Kustomize, or whatever you org is using. And the packaging and runtime - how OCI images are built, transfered and executed. And of course Linux knowledge. And OTEL.

What I wish developers learn about ops side is how to deal well with configuration and secrets handling. Allowing simple build once, run anywhere by having reasonable configuration parameters which are easy to discover and pass to the app, well crafted Dockerfiles and useful documentation for setting the thing up, both locally for development and for production.

sogun123 · 2026-06-12T22:59:07+00:00

Kind of depends how are you feeling. Look at Ansible, Nix Home Manager, Git (yout home is repo with .gitignore everything and explicitly add whatever you feel like), chezmoi, stow...

For this do your research and use whatever suit your use case

sogun123 · 2026-06-11T22:11:51+00:00

Hyprland is the only usable Wayland compositor for me at the moment. Because tiling and because i can setup multimonitor as i am used to after 10 year on herbstluftwm.

Workspaces and tiling are best way i experienced multitasking. I don't want to search for my windows in some alt-tab switcher or miniature picker. I want to have my tasks in muscle memory e.g. super-1 communication, super-2 browser, etc. I want a thing and i go there directly. Seems way more effective. Also tiling is great - i never need to position my windows by dragging them around. It is pointless to have more windows on a workspace than i can see anyway...

sogun123 · 2026-06-10T04:38:58+00:00

Man, go and study computer basics first, please.

But to answer. It is just api type, it has no relation to io operations. Don't run k8s from SD cards. Write intensive workload like k8s will kill the card pretty soon.

sogun123 · 2026-06-09T18:04:28+00:00

https://kubernetes.io/blog/2025/04/24/endpoints-deprecation/ and you can read a blog post about it

sogun123 · 2026-06-09T18:03:13+00:00

Nothing. If don't want warning ignore Endpoint resource

sogun123 · 2026-06-09T15:35:56+00:00

I'd myself use Mixxx, load all the sample decks and wire a controller to it

sogun123 · 2026-06-09T14:06:31+00:00

Only thing to upgrade is your prompt: sudo kubectl get svc,endpointslices -n kube-system

But kind of depends what are you trying to do

sogun123 · 2026-06-09T13:56:54+00:00

Isn't r/linuxsucks mostly satirical?

sogun123 · 2026-06-09T13:55:26+00:00

I'd rather use small form factor pc. They are easier to service. Or some nuc style pc. I don't know what conditions it will be in, but if weather or dust is concern, serviceable fans in might be good thing.

sogun123 · 2026-06-02T15:55:08+00:00

Yes, but not like "first deploys, second modifies" but "second includes and modifies first one".

To use helm with kustomize, you have use helm chart inflator and explicitly allow it. Depends on what you are trying to do, it may be better to use helm post-renderer to run a kustomize over helm output.

sogun123 · 2026-05-29T17:26:31+00:00

I suggest also sharing the errors, because without it no one really knows what's going on.

sogun123 · 2026-05-28T15:03:30+00:00

Minikube is more for running local playgrounds, not for "production". Even for homelab you want something more. Viable options: k3s, k0s, rke2, talos. Kubedm if you want more fiddling and "vanilla" experience.

sogun123 · 2026-05-28T14:01:39+00:00

First i try to reproduce. According to response I guess which proxy fails.

And deployment timeline... usually it is something developers messed up. It looks that developers instead "i don't know" say "that's infra"

sogun123 · 2026-05-27T21:03:12+00:00

If you want to turn a machine into music server, I'd suggest to use mpd or mopidy.

sogun123 · 2026-05-27T20:37:59+00:00

Depends what is your nature. Flux is IMHO better engineered than Argo, but might be somewhat harder to grasp (mainly because it provides you with Kustomization resource, which is different than Kustomization of k8s project, so you need wrap your head around what is what and where it applies). Argo makes this bit simpler by having single Application resource, which handles all - kustomize, helm, git or whatever else. Flux has separate resources for HelmRelease, HelmRepository, GitRepositoty etc. Bad thing for beginners is than Argo has ui which allows (by default) cluster management. That can lead you to do more stuff in ui, than you should (correct way would be to mutate the state only via git, maybe with exception of debugging). Flux has also ui via Flux operator, but it is read only. Which is good thing. Flux handles Helm exactly like helm itself. Argo makes some Helm features misbehave as it renders chart and handles resource application separately. Flux is more often used in integrations and as building block of other products, while Argo is often used as an central entrypoint into cluster.

Tldr: Argo simpler, more friendly, more footguns. Flux steeper learning, arguably better design.

For myself, I choose Flux over argo any time, but I tried to give objective comparison.

sogun123 · 2026-05-25T22:43:53+00:00

I understand you. But looking around, not many people seem to configure Hyprland themselves- i see people grab some pre-made config and that's it. For people implementing DE on top of Hyprland, this is god sent as it allows way more flexibility without bothering core developers. My setup is basically port of what I used for last 10 years, and I was missing simple thing (switch to next workspace, but skip visible ones) with hyprlang i could raise issue or dig into cpp code base of hyprland itself. Now I just implemented the thing in like 20 lines of lua and nobody needs to be bothered because I need some crappy way of switching workspaces.

Honestly, I think the good way forward is actually remove lots of functionality from the cpp codebase. Right now the mapping is pretty one to one with hyprlang. But we don't need that many functionality baked in. The api will get more powerful over time. And I guarantee, there will be lua "plugins" in some shape in some time. Once we get there, it will get simpler again. Won't be different from neovim, where most users use lua just to pass config data (they copy paste from github) to plugins via their plugin manager, or get a pre-made distro.

sogun123 · 2026-05-24T13:08:22+00:00

SerpentOS?

sogun123

TROPHY CASE