As of you are using Rancher the easiest way would be to register custom Rancher Catalog and create an item for each stack/service you want to deploy.
Rancher Catalog is a Git repository with the following structure
Then in Jenkins you can create a job that would call Rancher REST API to deploy/update stack/service.
In its turn Rancher would pull latest ...
I've seen this happen, especially on the newest (as of now) version. Try going into the "Infrastructure stack" and look for stopped containers. Often it helps to just refresh the entire deployment (hit the button "up to date" next to the "kubernetes" stack and hit save (If I remember correctly) in the bottom to force the "refresh").
You could also try ...
(Rancher employee) Kubernetes itself is really not meant for that use-case. A cluster is generally a set of machines in the same provider with close proximity (latency) to each other.
Etcd (and therefore API/CLI/UI/scheduling/everything) performance depends heavily on the (worst-case) latency between all members.
Only one cloud-provider integration (...
ibuildthecloud9 gave me the right hint. Since the github issue doesn't describe how to midify the dns, I figured it out and want to document it here in case someone need to change it, too. It's stored in the configmap coredns as Corefile:
proxy . 220.127.116.11
You need to replace this by your dns server (192.168.0.19 in my case). It could be done manually using ...
You haven't specified anything concrete, so I can't give you a specific reason... But catalog items can:
Be mutually exclusive (e.g. you can't use ipsec and vxlan at the same time)
Be deployed at most once in an environment
Require the environment be a specific orchestration type
Require a certain range of Rancher versions
Project is a Rancher specific concept. A Project can have multiple Kubernetes namespaces.
The System Project has all the Kubernetes system components like kube-dns, ingress etc. Think of it like System Services running on a machine/laptop.
Default project is where you can launch your workloads to start with. Similar to a scratchpad.
You can create new ...
The short answer is "it depends". Rancher itself runs using system-docker and the docker instances it starts for you, such as gitlab-runner are run separately in regular docker. Gitlab-runner then will start runners depending on its configuration:
There are three methods to enable the use of... docker run during
jobs; each with their own tradeoffs.
First of all you need to support HA mode. You will need:
external MySQL DB (e.g. AWS RDS Aurora)
external load balancer (e.g. AWS ELB)
2 additional Rancher Server Nodes (to support quorum of 3)
Once you will be ready with external DB Rancher would ask you to backup & restore his database in it. After that you'll be asked to redeploy Rancher Server with ...