The folder contains:
- configure-rancher-server-version.sh -> the script that will modify the version to be used for installing Rancher
- configure-cert-manager-version.sh -> the script that will modify the version to be used for installing cert-manager
- Makefile -> the file contains a series of shortcuts for deploying the Kubernetes resources of the various tools in the directory
- Tools directory (Example
rancher-server) -> the folder contains custom resources, such as theresources/custom-helm-values.yamlfile, which will override the base configurations
- a working Kubernetes cluster -> and consequently exports the KUBECONFIG variable
- ensure you have reviewed the Rancher Support Matrix and that your cluster meets the suggested hardware requirements
- configure the rancher-server/resources/custom-helm-values.yaml file as you see fit -> this setup works perfectly in the Cloud environment, as the
rancherK8s Service of typeLoadBalancerwill automatically create a Cloud LB and assign an external IP to reach the Rancher URL
sh configure-rancher-server-version.sh -r rancher_releasesh configure-cert-manager-version.sh -r cert-manager_releaseThese scripts work perfectly from the macOS terminal; if you use any other Linux distribution, remove '' from the sed command.
make install-cert-manager
make install-rancher-servermake upgrade-rancher-servermake uninstall-rancher-server
make uninstall-cert-managerAfter launching the Rancher uninstallation command, which is nothing more than a Kubernetes Job that cleans up all the Namespaces and Pods created by Rancher itself, the kubectl logs command is executed to follow all the cleaning steps.
You can stop viewing the logs by clicking "control + c" and restart them by relaunching the uninstall command.