-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
The plugin allows to use service accounts only when running in Kubernetes. However, service accounts can be used to access a kubernetes cluster from outside as well. See [1].
To connect a Jenkins instance to an existing kubernetes cluster, it would be very natural for an admin to create a dedicated service account, assign it to a namespace and make use of it to configure the kubernetes plugin.
Since the functionality is already there, I guess the effort would not be to high. Or is there any reason not to do so?
- is duplicated by
-
JENKINS-49660 Unable to configure plugin using ibm k8s
-
- Resolved
-
csanchez I agree with nitinpadalia When you add this type of Kubernetes Service Account in the Jenkins UI there is no Value field so it shows "Secret text" and you have no control over the value to add the serviceaccount name used or add a token needed for that serviceaccount name.
Anyway to validate with 1.12.0 and 1.12.4 with LTS 2.121.3