jeffersonbienaime@JefferscBookPro ~ % kubectl -n cattle-system describe ingress
Name: rancher
Namespace: cattle-system
Address: 20.121.157.157
Default backend: default-http-backend:80 (<error: endpoints “default-http-backend” not found>)
TLS:
tls-rancher-ingress terminates
rancher.momanceanalytics.com
Rules:
Host Path Backends
---- ---- --------
rancher.momanceanalytics.com
rancher:80 (10.244.1.24:80,10.244.1.25:80,10.244.1.26:80)
Annotations:
cert-manager.io/issuer: rancher
cert-manager.io/issuer-kind: Issuer
field.cattle.io/publicEndpoints:
[{“addresses”:[“20.121.157.157”],“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 29m cert-manager Successfully created Certificate “tls-rancher-ingress”
Normal Sync 27m (x3 over 29m) nginx-ingress-controller Scheduled for sync
jeffersonbienaime@JefferscBookPro ~ % 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.7.0
heritage=Helm
release=rancher
Annotations: <none>
API Version:
cert-manager.io/v1
Kind: Certificate
Metadata:
Creation Timestamp: 2023-01-09T22:53:52Z
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💹
f:heritage:
f:release:
f😮wnerReferences:
.:
k:{“uid”:“01b90500-07bb-4261-8397-28c757ff0964”}:
f😒pec:
.:
f:dnsNames:
f:issuerRef:
.:
f:group:
f:kind:
f:name:
f😒ecretName:
f:usages:
Manager: controller
Operation: Update
Time: 2023-01-09T22:53:52Z
API Version:
cert-manager.io/v1
Fields Type: FieldsV1
fieldsV1:
f😒tatus:
.:
f:conditions:
f:lastFailureTime:
Manager: controller
Operation: Update
Subresource: status
Time: 2023-01-09T22:55:20Z
Owner References:
API Version:
networking.k8s.io/v1
Block Owner Deletion: true
Controller: true
Kind: Ingress
Name: rancher
UID: 01b90500-07bb-4261-8397-28c757ff0964
Resource Version: 25969
UID: 036b78b0-4a3d-485e-ac91-e17cf47cee9d
Spec:
Dns Names:
rancher.momanceanalytics.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: 2023-01-09T22:55:20Z
Message: The certificate request has failed to complete and will be retried: Failed to wait for order resource “tls-rancher-ingress-scrr7-4068673704" to become ready: order is in “invalid” state:
Observed Generation: 1
Reason: Failed
Status: False
Type: Issuing
Last Transition Time: 2023-01-09T22:53:52Z
Message: Issuing certificate as Secret does not exist
Observed Generation: 1
Reason: DoesNotExist
Status: False
Type: Ready
Last Failure Time: 2023-01-09T22:55:20Z
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Issuing 29m cert-manager Issuing certificate as Secret does not exist
Normal Generated 29m cert-manager Stored new private key in temporary Secret resource “tls-rancher-ingress-ffdjk”
Normal Requested 29m cert-manager Created new CertificateRequest resource “tls-rancher-ingress-scrr7”
Warning Failed 28m cert-manager The certificate request has failed to complete and will be retried: Failed to wait for order resource “tls-rancher-ingress-scrr7-4068673704" to become ready: order is in “invalid” state: