On Mon, Jan 22, 2018 at 11:27 PM, Chris Denneen wrote:
> 1. I was using the external name rather than the internal (cluster.local)
> DNS name in the Kubernetes Cloud Configuration in Jenkins
> 2. Even when I switched it appears it's because the port is necessary (
> http://jenkins.jenkins.svc.clu
1. I was using the external name rather than the internal (cluster.local)
DNS name in the Kubernetes Cloud Configuration in Jenkins
2. Even when I switched it appears it's because the port is necessary
(http://jenkins.jenkins.svc.cluster.local:443) which I found in open issue
(https://issues.jen
jnlp:
Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to
alter the behavior
Warning: SECRET is defined twice in command-line arguments and the
environment variable
Warning: AGENT_NAME is defined twice in command-line arguments and the
environment variable
Jan 22, 2018 9:27:
Yes you are missing the container name at the end
kubectl logs jenkins-slave-1kl4v-flv53 golang
On Mon, Jan 22, 2018, 21:01 Chris Denneen wrote:
> I've installed latest LTS of jenkins and installed latest
> kubernetes-plugin.
>
> I've created 2 pipeline jobs to test:
>
> pod-golang from here (
I've installed latest LTS of jenkins and installed latest kubernetes-plugin.
I've created 2 pipeline jobs to test:
pod-golang from here (
https://kumorilabs.com/blog/k8s-6-integrating-jenkins-kubernetes/)
and one from Carlos Sanchez blog here (
https://blog.csanchez.org/2016/10/25/jenkins-kuberne
