It's unclear to me why the Kubernetes plugin requires so much configuration. In general, Jenkins should be able to talk to Kubernetes with a KUBECONFIG and nothing else. Yet, when I give it a KUBECONFIG via a Jenkins secret, it still seems to connect to 'kubernetes.svc.default' which seems incorrect to me.
(Also, I didn't want to open a new bug for this, but why does this setup require the Jenkins instance to have port 5000 open? That's an operational burden for me...)
|Field||Original Value||New Value|
|Issue Type||Bug [ 1 ]||New Feature [ 2 ]|
|Summary||Kubernetes Plugin requires too much configuration||Accept kubeconfig file as credentials|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|