This message was deleted.
# generala
adamant-kite-43734
09/13/2023, 11:48 AMThis message was deleted.
f
full-wire-66533
09/13/2023, 11:49 AMMetrics Server looks good so far:#
full-wire-66533
09/13/2023, 11:50 AMAnyone else experiencing issues like that?
full-wire-66533
09/13/2023, 11:52 AMAlso two helm-operations ran into an error state with:
Copy code
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Timeout waiting for kubernetess
swift-sunset-4572
09/13/2023, 2:14 PMCorrect me if i am wrong but by Rancher Manager you mean Rancher UI on rke2 cluster ?
f
full-wire-66533
09/13/2023, 2:14 PMYes, correct.
s
swift-sunset-4572
09/13/2023, 2:23 PMBro try to install rancher with these steps
Copy code
# on the initial master
# add helm
curl -#L <https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3> | bash
# add needed helm charts
helm repo add rancher-latest <https://releases.rancher.com/server-charts/latest>
helm repo add jetstack <https://charts.jetstack.io>
# add the cert-manager CRD
kubectl apply -f <https://github.com/jetstack/cert-manager/releases/download/v1.6.1/cert-manager.crds.yaml>
# helm install jetstack
helm upgrade -i cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace
# helm install rancher
helm upgrade -i rancher rancher-latest/rancher --namespace cattle-system --version=2.7.6swift-sunset-4572
09/13/2023, 2:23 PM Copy code
kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{.data.bootstrapPassword|base64decode}}{{"\n"}}'swift-sunset-4572
09/13/2023, 2:25 PMSo this is basically a rancher ui installation with self signed certificate
f
full-wire-66533
09/13/2023, 2:39 PMThanks! This is basically what I am doing actually. I have to set some further proxy variables, because I am behind a Proxy server, but this is fine I think. The
cert-manager-startupapicheck Copy code
Error from server (InternalError): Internal error occurred: failed calling webhook "<http://webhook.cert-manager.io|webhook.cert-manager.io>": failed to call webhook: Post "<https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s>": context deadline exceededfull-wire-66533
09/13/2023, 2:39 PMI saw similar errors before - is something broken regarding my network configurations?
full-wire-66533
09/13/2023, 2:41 PMOn installing the Rancher helm chart sometimes I see:
Copy code
Error: Internal error occurred: failed calling webhook \"<http://validate.nginx.ingress.kubernetes.io|validate.nginx.ingress.kubernetes.io>\": failed to call webhook: Post \"<https://rke2-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1/ingresses?timeout=10s>\": context deadline exceededs
swift-sunset-4572
09/13/2023, 2:42 PMCan you show me the steps you used for deploying the rke2 cluster ?
swift-sunset-4572
09/13/2023, 2:43 PM Copy code
RANCHER RKE2
-------
Master Node configuration
curl -sfL <https://get.rke2.io> | sh -
systemctl enable rke2-server.service
systemctl start rke2-server.service
systemctl status rke2-server.service
cd /usr/local/bin
cp /var/lib/rancher/rke2/bin/kubectl .
cp /var/lib/rancher/rke2/bin/crictl .
kubectl get nodes
Token is in --> cat /var/lib/rancher/rke2/server/node-token
cp /var/lib/rancher/rke2/bin/* /usr/local/bin/
Rancher Add the master node to the existing one -
curl -sfL <https://get.rke2.io> | INSTALL_RKE2_TYPE="server" sh -
systemctl enable rke2-server.service
mkdir -p /etc/rancher/rke2/
vim /etc/rancher/rke2/config.yaml --->
server: <https://atl20er8k8poc01.amer.prgx.com:9345>
token: K101d1721c1d7f2e6f0010076a43575dda9421f95a59c06cd401d0869fba8f8e4e5::server:d3271e27614df319d859be7ec0261cd2
systemctl start rke2-server.service
systemctl status rke2-server.service
For installing the Agent / worker node --> It will be same as adding the additional master node but only the INSTALL_RKE2_TYPE='agent' , everything else will remain the same
curl -sfL <https://get.rke2.io> | INSTALL_RKE2_TYPE="agent" sh -f
full-wire-66533
09/13/2023, 2:46 PMNo I don´t think so.
full-wire-66533
09/13/2023, 2:47 PMI changed some configs using the config-file.
full-wire-66533
09/13/2023, 2:49 PMThis is my /etc/rancher/rke2/config.yaml
Copy code
server: <https://t-lb>.***.**>:9345
token: *****
data-dir: /****/rancher/rke2
cni: canal
tls-san:
- cluster.local
- t-lb.***.**
snapshotter: overlayfs
node-name: t-rch-m01.***.**full-wire-66533
09/13/2023, 2:51 PMThe server
<https://t-lb>.***.**full-wire-66533
09/13/2023, 2:53 PMAnd I added an environment file containing my proxy configuration. With HTTP_PROXY, HTTPS_PROXY and NO_PROXY vars.
s
swift-sunset-4572
09/14/2023, 6:49 AMDo a simple rke2 setup first and then proceed from there node name , data-dir are not so important field
swift-sunset-4572
09/14/2023, 6:50 AMTry installing it using the steps i provided you can later add the lb to your cluster
swift-sunset-4572
09/14/2023, 6:50 AMThe steps I provided to you are the same i am using in my prod environment and it runs fine . any modification you want to do you can take it as a day-2 activity instead
f
full-wire-66533
09/15/2023, 6:05 AMThanks Aditya, you are completely right. I will start a bit smaller again and come back.