Apex Dynamo

0 Followers
45 Following
16 Posts
GNU/Linux, Cloud infrastructure, FOSS

Hi,

I need to set up a proxmox cluster with 3 servers on OVH and deploy Kubernetes cluster (master and nodes) within the VMs inside Proxmox.

Any advice would be great. Thanks!

PS:
- I know that it is possible to have a Proxmox cluster but this will be my 1st time and I don't know more than that yet

- Yes, I exactly need this setup instead of the Managed Kubernetes Service ๐Ÿ™‚

- It has to be production-ready and the app deployed on Kubernetes are user-facing

scripts/xz_cve-2024-3094-detect.sh at refs/heads/main ยท cyclone-github/scripts

Scripts by cyclone to automate tasks. Contribute to cyclone-github/scripts development by creating an account on GitHub.

GitHub
@amberage @jbzfn
Bureaucratic strategy ... ๐Ÿ˜ž
I think they might even raise your salary then after finding someone who can barely replace you, they will complain about the budget and say they have to fire you because you are very expensive with not that great ROI ...
You really have to not fall with the "We are all a big family here".
If they won't fire you directly, they will find another way.
@ifiinlist Copy/paste of the multitasking definition ?
@kwf there is the other CentOS ๐Ÿ˜” their CentOS...
@beansthefrog ask systemd if they don't have a solution to your pbm ๐Ÿซฃ
@maxinehayes I see failed=0
And I don't see the ansible "createrepo" task... Can you elaborate more on your issue ?
@nixCraft
Funny ๐Ÿคฃ Windows shouldn't have asked ๐Ÿซฃ

@tasket
Hey, you're right, Linux is a kernel !

Systemd is a component (an extra) on which we need to have our choice to go for it or not.

And obviously you can't compare an extra tool to a kernel (And yet, you can't compare it to coreutils which are the core utilities to interact with the system ๐Ÿ˜‹โ€‹)

I don't want to debate for or against Systemd. Yeah it's powerful and I respect its developers because I am using it on many servers. But compared to its alternatives, it's just too complex for me.

It would just be better to have choices and avoid something like vendor-lock in for crucial component.
Also, I want things simpler because my work on these system are already not that trivial.

@shine @sonny @pid_eins

I'll explain my concerns.

- At first, I thought that it was just an alternative to sysvinit, runit ... even though existing init systems / process managers were fine.
The freedom of choice like we all want to have.
But no! It's not just a init thing. It's about controlling the system. Note that I felt in love with the name.

- Systemd : 1 package with many functionalities (tools) controling many building block for a Linux system (part of this definition came from its website)

- No code is really bullet-proof, and a single package that has control over many parts of the system can lead to a larger attack surface and a bigger impact IMHO, No ?

- And hey, why the heck do we have to deal with binary log ?
Why not the usual plain text stream. We have to rely on systemd tool to operate on them. As a sysadmin I have to do some "witchery" operations on logs stream and it is not helpful in many cases as I want to use other tools for some direct manipulation on it.

- Speaking about choice, will we always have the choice to go for another init system if the packages in the distribution we used to work on is totally dependent on systemd ? What if this extends to the whole Linux community ?

Doesn't it sound like a kinda systemd-centric ?
Couldn't it be a bit freaky ?
Where is the good old "Free" ?
Adding to that, the "Open Source" starts to fade on some software that used to be Open, actually.

- All of that doesn't help for saying that systemd will make Linux a better OS.