[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title davidkarlsen commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API what's strange also is that this only happens when declaring a yaml/yamlFile in a declarative pipeline, not if it is defined as a podTemplate on jenkins master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.2669.1567084620289%40Atlassian.JIRA.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Change By: Jesse Glick Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.12987.1563306217792%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
yes Yes that is in my {{-Dno.Proxy kubernetes.default.svc,...}} that starts Jenkins .{{APISERVER=https://kubernetes.default.svc}} in the curl command.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.63.1557515100226%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API yes that is in my -Dno.Proxy kubernetes.default.svc,... that starts Kenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.55.1557514861397%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
yes that is in my {{-Dno.Proxy kubernetes.default.svc,...}} that starts Kenkins Jenkins
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.57.1557514861462%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Carlos Sanchez commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API so you don't want https://kubernetes.default.svc to go through the proxy, correct? do you have -Dno.Proxy=kubernetes.default.svc,somethingelse ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.47.1557514740183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Yeah been there looked at that also.I am now running Jenkins using the following java properties:{code:java}-Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx{code}Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in:{code:java}Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502{code}and the following log entry on the proxy server:{code:bash}1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 -{code}Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy' button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated:{code:java}Failed to connect to https://kubernetes.default.svc.javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330){code}From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:{code:bash}curl $APISERVER/api/v1/namespaces/pd-dgames-test/pods/ --header "Authorization: Bearer $TOKEN" --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt{code}Kubernetes plugin spinning up a slave repeatedly gives me this:{code:java}May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed to count the # of live instances on Kubernetesjava.io.IOException: Unexpected response code for CONNECT: 502at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.java:389)at okhttp3.internal.connection.RealConnection.connectTunnel(RealConnection.java:211)at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:152)at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)at
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Yeah been there looked at that also.I am now running Jenkins using the following java properties:{code:java}-Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx{code}Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in:{code:java}Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502{code}and the following log entry on the proxy server:{code:bash}1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 -{code}Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy ' button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated:{code:java}Failed to connect to https://kubernetes.default.svc.javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330){code}From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:{code:bash}curl $APISERVER/api/v1/namespaces/pd-dgames-test/pods/ --header "Authorization: Bearer $TOKEN" --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt{code}Kubernetes plugin spinning up a slave repeatedly gives me this:{code:java}May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed to count the # of live instances on Kubernetesjava.io.IOException: Unexpected response code for CONNECT: 502at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.java:389)at okhttp3.internal.connection.RealConnection.connectTunnel(RealConnection.java:211)at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:152)at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)at
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API I am now running Jenkins using the following java properties: -Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in: Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502 and the following log entry on the proxy server: 1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 - Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated: Failed to connect to https://kubernetes.default.svc. javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330) From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Yeah been there looked at that also. I am now running Jenkins using the following java properties:{code:java}-Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx{code}Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in:{code:java}Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502{code}and the following log entry on the proxy server:{code:bash}1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 -{code}Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated:{code:java}Failed to connect to https://kubernetes.default.svc.javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330){code}From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:{code:bash}curl $APISERVER/api/v1/namespaces/pd-dgames-test/pods/ --header "Authorization: Bearer $TOKEN" --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt{code}Kubernetes plugin spinning up a slave repeatedly gives me this:{code:java}May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed to count the # of live instances on Kubernetesjava.io.IOException: Unexpected response code for CONNECT: 502at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.java:389)at okhttp3.internal.connection.RealConnection.connectTunnel(RealConnection.java:211)at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:152)at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)at
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Carlos Sanchez commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Also see issue in kubernetes-client library https://github.com/fabric8io/kubernetes-client/issues/1335 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.23121.1557472020279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Carlos Sanchez commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API If you are talking about the communication between Jenkins and Kubernetes API the following system properties are used to configure proxy http.proxy https.proxy no.proxy proxy.username proxy.password https://github.com/fabric8io/kubernetes-client/blob/9e850ad769134566e32f8c41498e5e64ecf8b799/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/Config.java#L106 You can see a test that is passing here https://github.com/jenkinsci/kubernetes-plugin/pull/477 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.23116.1557471300243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games updated an issue Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Change By: Dax Games Comment: Carlos/Plugin Maintainers,Can we have a way to pass proxy and no_proxy settings from the Jenkins master to the Kubernetes slave?Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.22563.1557435420190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API I found this code that passes the master env vars related to proxy settings to the slave. The problem is the pod never starts because the plugin can't talk to the Kubernetes API because it ignores the no_proxy settings. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.22558.1557435300164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games updated an issue Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Change By: Dax Games Summary: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.22553.1557435060294%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games edited a comment on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations Carlos/Plugin Maintainers,Can we have a way to pass proxy and no_proxy settings from the Jenkins master to the Kubernetes slave?Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.22469.1557431100136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations Carlos/Plugin Maintainers, Can we have a way to pass proxy settings from the Jenkins master to the Kubernetes slave? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.22464.1557430620225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Steve Collins edited a comment on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I also have this problem when the docker image has 'no_proxy' set in the image.I had to remove the no_proxy env var from the image to be able to set no_proxy using Env/Node/etc properties.This was not a good workaround as it pushed proxy info back to the user (100's of Jenkins) and not able to use as we hope in other contexts outside of Jenkins without passing in no_proxy env var.thanks. Plugin is really great! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Steve Collins commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I also have this problem when the docker image has 'no_proxy' set in the image. I had to remove the no_proxy env var from the image to be able to set using Env/Node/etc properties. This was not a good workaround as it pushed proxy info back to the user (100's of Jenkins) and not able to use as we hope in other contexts outside of Jenkins without passing in no_proxy env var. thanks. Plugin is really great! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Viktor K commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I have exactly the same problem..Could you please let us know what is the problem here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations Any word on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations Any word on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games updated an issue Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' configurations Change By: Dax Games Summary: Kubernetes plugin does not respect 'no_proxy' environment variable. configurations Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
