Hot answers tagged

16

First of all, Rancher actually contains implementations of both Kubernetes and Mesos within itself. However, they did make their own system called Cattle which is heavily based on Docker's Swarm. I'll touch upon this in the section for Rancher. Secondly, since each one offers similar base features (load balancing, resource isolation, etc) I'll try to go ...


4

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 ...


3

It depends on what your persistentVolumeReclaimPolicy is. If you manually created/defined the PersistentVolume, then the default action is to keep the data. (This sounds like what you're doing.) If you are using something like EKS on Amazon, your PV's are dynamically generated EBS volumes. In that case, they will be deleted by default. A little bit more ...


3

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 . 1.1.1.1 You need to replace this by your dns server (192.168.0.19 in my case). It could be done manually using ...


3

I believe this is an current bug in k3s that upstream DNS is hardcoded to 1.1.1.1. this should be resolved shortly https://github.com/rancher/k3s/issues/53


2

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 ...


1

If you could let us know what helm chart you have used to install prom-operator, that might help refine the answer. But in case of kube-prometheus-stack, in the values.yaml of the , use the additionalScrapeConfigs section to describe jobs that are external to k8s system and re-deploy. Or use serviceMonitors as described in this article


1

In my opinion, your real problem about this is getting incomplete data that didn't include image scanning, hardening and trusted registries. Here are some first directions: The well curated Official Docker Images on DockerHub You can setup trusted docker registries and setup docker clients to evaluate these based on content trust. If you are planning to ...


1

You might have better luck finding answers to your questions if you use the more standard term of "containerization". This article discusses containerization as well as some pros and cons you might want to consider.


1

See my answer here: Ran into this today when trying to use Garden.io for a cluster running in Jelastic. Found the solution in this Github comment: First acquire a local binary for Tiller (server-version of Helm), either by compiling or by downloading it from the release page. Then run: $ export HELM_HOST=":44134" $ tiller -listen ${HELM_HOST} -...


1

(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 (...


1

Your first step is to setup and configure the Route53 service from the rancher catalog. After that, the load-balancer will automatically update its DNS in Route53.


1

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 ...


1

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. ...


1

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 ...


1

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 etc


Only top voted, non community-wiki answers of a minimum length are eligible