[JIRA] (JENKINS-60574) Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin

5 views
Skip to first unread message

konstantin.satunin@gmail.com (JIRA)

unread,
Dec 23, 2019, 8:51:02 AM12/23/19
to jenkinsc...@googlegroups.com
Konstantin Satunin created an issue
 
Jenkins / Bug JENKINS-60574
Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin
Issue Type: Bug Bug
Assignee: Unassigned
Components: kubernetes-plugin
Created: 2019-12-23 13:50
Priority: Major Major
Reporter: Konstantin Satunin

After introduction of direct connection option in kubernetes plugin and remoting it's now possible to avoid http(s) requests to jenkins host.

But if you want to connect agents which are tunneled, it's not possible to utilize direct connection because kubernetes plugin uses Jenkins host and port reported by TCP agent listener.

https://github.com/jenkinsci/kubernetes-plugin/blob/33737fe0c96615e33b78205fe6e71aaffca2df49/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplateBuilder.java#L345

 

Currently there are no way to modify JENKINS_DIRECT_CONNECTION in the container using podTemplate because PodTemplateBuilder overrides any environment variables.

 

Proposal

Introduce one more property "Direct connection endpoint" in the cloud configuration under Direct Connection settings and allow to set it to be set to host:port string.

If this direct connection endpoint was not set, use default values from TcpSlaveAgentListener like its done now.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

konstantin.satunin@gmail.com (JIRA)

unread,
Dec 23, 2019, 9:11:03 AM12/23/19
to jenkinsc...@googlegroups.com

vincent@latombe.net (JIRA)

unread,
Jan 24, 2020, 9:31:04 AM1/24/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages