To experiment the deployment of the services in kubernetes, it will be more convenient for @amadouth6
to have a real cluster to perform his tests
Description
Description
Revisions and Commits
Revisions and Commits
rSPRE sysadm-provisioning | |||
D7740 | rSPREd62700b98e98 Refresh staging.tfstate after the new kubernetes cluster creation | ||
D7740 | rSPRE0ff550d0f889 Declare the rancher cluster for the deployment's internship | ||
D7740 | rSPRE529a2d63d236 refresh elastic-workers cluster after accidentally elastic-worker0 removal | ||
D7740 | rSPREd43e6bb05d85 Ensure cloud-init is not running before starting puppet | ||
D7740 | rSPRE062ec99d2101 Align worker0 and worker1 qemu arguments to match the real vms configuration | ||
rSPSITE puppet-swh-site | |||
D7739 | rSPSITEb8ef7d1655b1 Declare the vagrant ips of the recently created nodes | ||
D7739 | rSPSITEf58f988f25cc Declare a generic rancher-node-.* hostname matching | ||
D7739 | rSPSITEd4d32f417106 kubernetes: Declare a generic rancher_node profile |
Related Objects
Related Objects
Event Timeline
Comment Actions
The cluster is declared and the node provisionning.
The cluster information can be found in rancher [1]
[1] https://rancher.euwest.azure.internal.softwareheritage.org/