KuberLogic cert-manager issue about kuberlogic

[ynnt]

Hi

What version of kuberlogic are you running?

[sarthakdixit89]

Hi,
KuberLogic version
cli: 0.0.12
I am currently using this version.

[ynnt]

Could you please run this command and provide the generated zip file

kuberlogic diag

[sarthakdixit89]

Created Zip after using cmd "kuberlogic diag"
kuberlogic-diag-1663058341.zip

[sarthakdixit89]

Hi,
May you please share what will be the diagnose by my shared https://github.com/kuberlogic/kuberlogic/files/9555092/kuberlogic-diag-1663058341.zip?

[ynnt]

Please also share this command output kubectl -n cert-manager describe pods

[sarthakdixit89]

kubectl -n cert-manager describe pods
Name: cert-manager-66bd77df8f-fnnm2
Namespace: cert-manager
Priority: 0
Service Account: cert-manager
Node:
Labels: app=cert-manager
app.kubernetes.io/component=controller
app.kubernetes.io/instance=cert-manager
app.kubernetes.io/name=cert-manager
app.kubernetes.io/version=v1.7.1
pod-template-hash=66bd77df8f
Annotations: prometheus.io/path: /metrics
prometheus.io/port: 9402
prometheus.io/scrape: true
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/cert-manager-66bd77df8f
Containers:
cert-manager:
Image: quay.io/jetstack/cert-manager-controller:v1.7.1
Port: 9402/TCP
Host Port: 0/TCP
Args:
--v=2
--cluster-resource-namespace=$(POD_NAMESPACE)
--leader-election-namespace=kube-system
Environment:
POD_NAMESPACE: cert-manager (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-tlbh2 (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
kube-api-access-tlbh2:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Warning FailedScheduling 52s default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.

Name: cert-manager-cainjector-6495667ff4-wc7fc
Namespace: cert-manager
Priority: 0
Service Account: cert-manager-cainjector
Node:
Labels: app=cainjector
app.kubernetes.io/component=cainjector
app.kubernetes.io/instance=cert-manager
app.kubernetes.io/name=cainjector
app.kubernetes.io/version=v1.7.1
pod-template-hash=6495667ff4
Annotations:
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/cert-manager-cainjector-6495667ff4
Containers:
cert-manager:
Image: quay.io/jetstack/cert-manager-cainjector:v1.7.1
Port:
Host Port:
Args:
--v=2
--leader-election-namespace=kube-system
Environment:
POD_NAMESPACE: cert-manager (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-7vsw2 (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
kube-api-access-7vsw2:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Warning FailedScheduling 52s default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.

Name: cert-manager-webhook-59d6cdfb6f-hnbfp
Namespace: cert-manager
Priority: 0
Service Account: cert-manager-webhook
Node:
Labels: app=webhook
app.kubernetes.io/component=webhook
app.kubernetes.io/instance=cert-manager
app.kubernetes.io/name=webhook
app.kubernetes.io/version=v1.7.1
pod-template-hash=59d6cdfb6f
Annotations:
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/cert-manager-webhook-59d6cdfb6f
Containers:
cert-manager:
Image: quay.io/jetstack/cert-manager-webhook:v1.7.1
Port: 10250/TCP
Host Port: 0/TCP
Args:
--v=2
--secure-port=10250
--dynamic-serving-ca-secret-namespace=$(POD_NAMESPACE)
--dynamic-serving-ca-secret-name=cert-manager-webhook-ca
--dynamic-serving-dns-names=cert-manager-webhook,cert-manager-webhook.cert-manager,cert-manager-webhook.cert-manager.svc
Liveness: http-get http://:6080/livez delay=60s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:6080/healthz delay=5s timeout=1s period=5s #success=1 #failure=3
Environment:
POD_NAMESPACE: cert-manager (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hwjqj (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
kube-api-access-hwjqj:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Warning FailedScheduling 52s default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.

[ynnt]

Your Kubernetes cluster does not have capacity to run containers.

[turmyshevd]

@sarthakdixit89 please drop me a line at [email protected], I'll send you a video instruction on KuberLogic installation