https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
c
Here's my steps:
Copy code
helm repo add rancher-stable <https://releases.rancher.com/server-charts/stable>
kubectl create namespace cattle-system

helm install rancher rancher-stable/rancher --version=$RANCHER_VERSION \
  --namespace cattle-system \
  --set hostname=${DOMAIN} \
  --set replicas=${REPLICAS} \
  --set bootstrapPassword="${BOOTSTRAP_PASSWORD}" \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=${ADMIN_EMAIL}
I installed ingress-nginx 4.2.0
Let's Encrypt 1.5.1
Kubernetes GKE 1.22
s
c
Yes, the only thing that seems to be different is the ingress-nginx version. That doc refers to 3.12.0, I'd like to use 4.2.0
I've also tried using 3.12.0 but get the same result
s
what errors are you seeing
c
I've been troubleshooting this on two different clusters. Here's one of the errors:
Copy code
[FATAL] failed to update <http://clusters.cluster.x-k8s.io|clusters.cluster.x-k8s.io> <http://apiextensions.k8s.io/v1|apiextensions.k8s.io/v1>, Kind=CustomResourceDefinition for  <http://clusters.cluster.x-k8s.io|clusters.cluster.x-k8s.io>: <http://CustomResourceDefinition.apiextensions.k8s.io|CustomResourceDefinition.apiextensions.k8s.io> "<http://clusters.cluster.x-k8s.io|clusters.cluster.x-k8s.io>" is invalid: status.storedVersions[0]: Invalid value: "v1beta1": must appear in spec.versions
s
try this
Copy code
helm upgrade --install \
  ingress-nginx ingress-nginx/ingress-nginx \
  --namespace ingress-nginx \
  --set controller.service.type=LoadBalancer \
  --version 4.2.0 \
  --create-namespace --set controller.watchIngressWithoutClass=true
You need the last flag in order for ingress to work properly.
c
Ok, thanks!
Gimme a sec
That did it! Thank you!
🎉 2
i
This helped me as well! God, I love searching through Slack Channels!
b
these are the commands I ran on gke
helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx \ --namespace ingress-nginx \ --set controller.service.type=LoadBalancer \ --version 4.2.0 \ --create-namespace \ --set controller.watchIngressWithoutClass=true
looks like its deployed but the command prompt is stuck
kubectl --namespace ingress-nginx get services -o wide -w ingress-nginx-controller NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR ingress-nginx-controller LoadBalancer 10.36.5.56 34.168.186.146 8032064/TCP,44331687/TCP 12m app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
s
I would recommend hiding your IP from any public forum like this
b
these are the exact steps I am following
just deployed rancher again with: helm install rancher rancher-stable/rancher \ --namespace cattle-system \ --set hostname=w-x-y.z.sslip.io \ --set replicas=3 \ --set ingress.tls.source=letsEncrypt
but still getting 404 error accessing ranher
rancher
s
you’re using letsencrypt, did you set your email for it? what (if any) pods/deployments have issues in your cluster?
b
all pods are up, deployment is fine. I jut cant bring up the rancher portal from the load balancer ip
s
did you try from the hostname you specify? Or check rancher logs? There should be something somewhere telling you there’s a problem
b
i was able to get version 2.6 working. Not sure what happened to 2.5.
to add existing gke cluster to rancher, do I need a service account?
58 Views
Open in Slack
PreviousNext
Powered by