hi every one,
I just create a new cluster on linode and I deploy rancher to that cluster v. 1.21. the installation finished successfully but still waiting for the web-ui its not coming.
##################
~$ curl http://rancher.mydomain.com/
curl: (28) Failed to connect to rancher.mydomain.com port 80: Connection timed out
~$ curl https://rancher.mydomain.com/
curl: (28) Failed to connect to rancher.mydomain.com port 443: Connection timed out
~$ kubectl -n cattle-system describe ingress
Name: rancher
Namespace: cattle-system
Address: 212.71.236.215
Default backend: default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
TLS:
tls-rancher-ingress terminates rancher.mydomain.com
Rules:
Host Path Backends
---- ---- --------
rancher.mydomain.com
rancher:80 (10.2.0.5:80,10.2.2.4:80,10.2.4.7:80)
Annotations: cert-manager.io/issuer: rancher
cert-manager.io/issuer-kind: Issuer
field.cattle.io/publicEndpoints:
[{"addresses":["212.71.236.215"],"port":443,"protocol":"HTTPS","serviceName":"cattle-system:rancher","ingressName":"cattle-system:rancher"...
meta.helm.sh/release-name: rancher
meta.helm.sh/release-namespace: cattle-system
nginx.ingress.kubernetes.io/proxy-connect-timeout: 30
nginx.ingress.kubernetes.io/proxy-read-timeout: 1800
nginx.ingress.kubernetes.io/proxy-send-timeout: 1800
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal CreateCertificate 58m cert-manager Successfully created Certificate "tls-rancher-ingress"
Normal Sync 52m (x3 over 58m) nginx-ingress-controller Scheduled for sync
~$ kubectl -n cattle-system describe certificate
Name: tls-rancher-ingress
Namespace: cattle-system
Labels: app=rancher
app.kubernetes.io/managed-by=Helm
chart=rancher-2.6.3
heritage=Helm
release=rancher
Annotations: <none>
API Version: cert-manager.io/v1
Kind: Certificate
Metadata:
Creation Timestamp: 2021-12-23T11:23:06Z
Generation: 1
Managed Fields:
API Version: cert-manager.io/v1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:labels:
.:
f:app:
f:app.kubernetes.io/managed-by:
f:chart:
f:heritage:
f:release:
f:ownerReferences:
.:
k:{"uid":"53768dfd-3e54-454c-9f2f-c9706c39d393"}:
.:
f:apiVersion:
f:blockOwnerDeletion:
f:controller:
f:kind:
f:name:
f:uid:
f:spec:
.:
f:dnsNames:
f:issuerRef:
.:
f:group:
f:kind:
f:name:
f:secretName:
f:usages:
f:status:
.:
f:conditions:
f:notAfter:
f:notBefore:
f:renewalTime:
f:revision:
Manager: controller
Operation: Update
Time: 2021-12-23T12:19:33Z
Owner References:
API Version: networking.k8s.io/v1
Block Owner Deletion: true
Controller: true
Kind: Ingress
Name: rancher
UID: 53768dfd-3e54-454c-9f2f-c9706c39d393
Resource Version: 17170
UID: 4af1f119-fde7-42c5-9179-6cf7a5185a1b
Spec:
Dns Names:
rancher.mydomain.com
Issuer Ref:
Group: cert-manager.io
Kind: Issuer
Name: rancher
Secret Name: tls-rancher-ingress
Usages:
digital signature
key encipherment
Status:
Conditions:
Last Transition Time: 2021-12-23T12:19:33Z
Message: Certificate is up to date and has not expired
Observed Generation: 1
Reason: Ready
Status: True
Type: Ready
Not After: 2022-03-23T11:19:31Z
Not Before: 2021-12-23T11:19:32Z
Renewal Time: 2022-02-21T11:19:31Z
Revision: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Issuing 56m cert-manager Issuing certificate as Secret does not exist
Normal Generated 56m cert-manager Stored new private key in temporary Secret resource "tls-rancher-ingress-cmjk8"
Normal Requested 56m cert-manager Created new CertificateRequest resource "tls-rancher-ingress-q8phh"
Normal Issuing 28s cert-manager The certificate has been successfully issued
##############################
I would appreciate any assistant in this regards,
if any further information needed I would provide.
I still couldn’t understand how could the web-ui acquire the certificate while I couldn’t reach it, haha