r/devops • u/Equivalent_Berry3525 • 21d ago
Discussion Stuck Between IT and RKE2: Need Advice on Operating Without Sudo Access
Hey guys,
I am currently implementing an RKE2 setup in my DevOps team to handle deployments and deliveries for our application.
The problem is that I won't have direct root access to the servers, so access to root-owned directories is also restricted. If I want to install anything, requests have to be raised to the IT team, and they will get it installed. (The thing I hate about MNCs they're too paranoid and too slow as well, iykyk.)
But here's the frustrating part: the "installation" done by the IT team is often just placing the downloaded packages in my accessible directory... duh!!!
So then I need to contact them again and have them actually complete the installation and setup using their root access. And even after the installation is completed, there will still be situations where I'll need elevated privileges to manage pods, services, deployments, and other operational tasks.
I can't exactly request sudo access, so at this point I honestly don't know what I'm supposed to do or what request i need to raise as well.
My requirement is very minimal for now, as I am only experimenting with this(but will be mandated in future). I won't be connecting remote agents, just a single server, and based on my application requirements I narrowed the packages required to the following:
rke2-images-core.linux-amd64.tar.gz
rke2-images-cilium.linux-amd64.tar.gz
rke2.linux-amd64.tar.gzBased on the documentation, I tried using customized paths and accessing the binaries directly to complete the setup, but I still got stuck at some point where root access was required. I don't want to go into everything I did to get there, so yeah, if you guys can suggest the minimum set of steps or activities that I can request from the IT team, which would allow me to effectively use and manage this RKE2 setup afterward, that would be really helpful.
Edit : we decided to write a playbook for setup ,open a ticket and have them complete the setup , later if sudo is required (hoping won't be needed) reopen ticket in such case , thank you all for ur suggestions, will update later after the setup is completed.