On Monday, October 24, 2016 at 11:52:12 AM UTC-4, Akagi Norio wrote: > > Hi, > > I'm trying to use Jenkins kubernetes plugin and want to make sure that if > this works even if Jenkins master is not inside a k8s cluster. > On all example on the internet I could find, people set a k8s api server's > address as a kubernetes service url, which can be resolved only within a > cluster. > > In my case I want to manage several k8s clusters (dev, stg, prod) from > Jenkins so Jenkins is outside of each cluster. > Although I put k8s API's reachable address from external, "test > connection" always shows "no route to host" errors. > > I checked my firewall setting but could not find a problem. I want to > confirm if my approach is valid. >
Yes, the Kubernetes plugin (plugin id "kubernetes") works whether the Jenkins host is part of the cluster or not, though configuration is more automatic when the Jenkins host is in the cluster. As you probably know, "no route to host" is an error from the IP layer. Can you connect to the Kubernetes URL from any host outside the cluster, such as via kubectl from your personal machine? From the Jenkins host, try pinging the host name or IP address from the Kubernetes URL. Try connecting to the URL manually using a tool like curl. Once you are able to get a response that way, move on to configuring Jenkins. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d67a8478-7ff7-4225-a1f4-de2e327a82fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
