rancher/rodeo

Rancher Rodeo Helm Chart Repository

This repository contains Helm charts that are used during Rancher Rodeo webinars and for demonstration purposes.

The Helm charts in this repository are not production ready and are meant for demonstration purposes only!

How to Use

Helm CLI:

helm repo add rodeo https://rancher.github.io/rodeo

Rancher:

• Go to the Apps Marketplace in Rancher
• Add a new Chart Repository to the HTTP(S) URL https://rancher.github.io/rodeo without authentication

How to Contribute

Create a pull request to the master branch. Make sure to bump the chart version in the Chart.yaml. Once the pull request is merged, a Github Action workflow will automatically build and package a new release of the changed charts and publish them to the chart repository.

rodeo's Issues

Include libvirt/kvm terraform

Who knows, maybe someone picks this up and helps poking on this other issue. Else, please close.

Cannot ping 172.22.101.101

I am trying to deploy Rancher using Vagrant/VirtualBox. Deployment is successful, but cannot ping the server ip. I did change the setting in config.yml to 'false'. I am doing this on Windows 10.

PS C:\Data\rancher\rodeo\vagrant> vagrant status
Config: {"default_password"=>"admin", "rancher_version"=>"v2.2.4", "cluster_name"=>"rodeo", "rodeo"=>false, "docker_version"=>{"server"=>"18.09", "node"=>"18.09"}, "server"=>{"cpus"=>1, "memory"=>2560}, "node"=>{"count"=>1, "cpus"=>2, "memory"=>3000}, "ip"=>{"server"=>"172.22.101.101", "node"=>"172.22.101.111"}, "linked_clones"=>true, "net"=>{"private_nic_type"=>"82545EM", "network_type"=>"private_network"}, "roles"=>{"node-01"=>"all"}}

Current machine states:

server-01 running (virtualbox)
node-01 running (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run vagrant status NAME.
PS C:\Data\rancher\rodeo\vagrant> ping 172.22.101.101

Pinging 172.22.101.101 with 32 bytes of data:
Reply from 146.61.102.253: Destination host unreachable.
Request timed out.

nfs-provisioner cannot create volumes

Hi,

No volumes can be successfully created after deployment of the nfs-provider example.

(...)
... I0222 17:47:28.036250 1 controller.go:407] Starting provisioner controller eb968de5-36c9-11e9-8af5-9ee6f721e4ce!
... E0222 17:47:28.038121 1 reflector.go:201] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:411: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:serviceaccount:nfs-client-provisioner:default" cannot list persistentvolumeclaims at the cluster scope
... E0222 17:47:28.038660 1 reflector.go:201] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:384: Failed to list *v1.StorageClass: storageclasses.storage.k8s.io is forbidden: User "system:serviceaccount:nfs-client-provisioner:default" cannot list storageclasses.storage.k8s.io at the cluster scope
(...)

Bye,
Thorsten

What order is guide run in?

There are several guide readme's in this directory

https://github.com/rancher/rodeo/tree/master/guide

What order are the guides supposed to be executed?

AWS Terraform Scripts - Docker not running after provisioning instances

Using Terraform v0.11.7

I successfully ran the terraform scripts, and the AWS instances were created. However, the Rancher dashboard did not come up.

I ssh'd into the master and ran docker ps, and docker was not running. I watched the docker ps command for about 10 minutes but nothing happened.

As a point of comparison, I ran the AWS Terraform scripts from https://github.com/rancher/quickstart successfully and was able to access the dashboard.

error: unable to recognize "nfs-client-provisioner.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

rodeo/k8s/nfs-client-provisioner.yaml

Line 50 in de304a3

apiVersion: extensions/v1beta1

Hash Sum mismatch fetching apt packages

Running vagrant up, I get this error:

E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/source/Sources.xz  Hash Sum mismatch
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/universe/source/Sources.xz  404  Not Found [IP: 91.189.88.149 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Full error output

    node-01:  apt-key add -
    node-01: OK
    node-01: + sh -c add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu xenial stable"
    node-01: + [ ubuntu = debian ]
    node-01: + sh -c apt-get update
    node-01: Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
    node-01: Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    node-01: Get:3 https://download.docker.com/linux/ubuntu xenial InRelease [66.2 kB]
    node-01: Ign:4 http://security.ubuntu.com/ubuntu xenial-security/main Sources
    node-01: Get:5 http://security.ubuntu.com/ubuntu xenial-security/restricted Sources [2116 B]
    node-01: Hit:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
    node-01: Get:7 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages [10.7 kB]
    node-01: Ign:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources
    node-01: Hit:9 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
    node-01: Get:10 http://archive.ubuntu.com/ubuntu xenial/main Sources [868 kB]
    node-01: Get:11 http://security.ubuntu.com/ubuntu xenial-security/multiverse Sources [3416 B]
    node-01: Get:4 http://security.ubuntu.com/ubuntu xenial-security/main Sources [153 kB]
    node-01: Err:4 http://security.ubuntu.com/ubuntu xenial-security/main Sources
    node-01:   Hash Sum mismatch
    node-01: Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [111 kB]
    node-01: Err:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources
    node-01:
    node-01: Get:12 http://archive.ubuntu.com/ubuntu xenial/restricted Sources [4808 B]
    node-01: Get:13 http://archive.ubuntu.com/ubuntu xenial/universe Sources [7728 kB]
    node-01: Get:14 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources [179 kB]
    node-01: Get:15 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [339 kB]
    node-01: Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/restricted Sources [2536 B]
    node-01: Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [260 kB]
    node-01: Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Sources [8764 B]
    node-01: Get:19 http://archive.ubuntu.com/ubuntu xenial-backports/main Sources [4848 B]
    node-01: Get:20 http://archive.ubuntu.com/ubuntu xenial-backports/universe Sources [7120 B]
    node-01: Fetched 9749 kB in 1min 12s (135 kB/s)
    node-01: Reading package lists...
    node-01: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/source/Sources.xz  Hash Sum mismatch
    node-01: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/universe/source/Sources.xz
    node-01: E: Some index files failed to download. They have been ignored, or old ones used instead.
    node-01: + usermod -aG docker vagrant
    node-01: usermod: group 'docker' does not exist
    node-01: + set -e
    node-01: + [[ -z true ]]
    node-01: + [[ true == \t\r\u\e ]]
    node-01: + exit 0