-
New Feature
-
Resolution: Unresolved
-
Major
-
None
At present only the Jenkins administrators can manage the available slaves/pods in a Kubernetes cloud. It makes much more sense to split the slaves/pods config into a separate configuration page and allow people with `slave` permissions to manage the different defined pods.
At present it is making the main configuration page too long to maintain as well puts the burden onto the administrators to manage any pod changes for the users.
- is related to
-
JENKINS-46003 Restrict ability to allow privileged containers to only exist in System Configuration
-
- Open
-
IMO Agent definitions should be Items like Jobs and others