sureshkachwa

Results 15 comments of sureshkachwa

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

@jelel-fliss I too have the same issue, cert-manager version is 1.6.1 and k8s cluster version is 1.20.1. For the first deployment certificate was issued but now for all the new...

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

I did the same but it didn't solve my problem, I still doubt, if it is something to do with ingress controller version or cert-manager version though same versions were...

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

> @sureshkachwa did you try a different version of cert-manager ? Before reloading the nginx-controller, I downgraded to the version 1.5.0. It still did not work after recreating the issuer...

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

@jelel-fliss still same issue. I'll give a try with new k8s cluster and cert-manager with version 1.5.0, edit the ing object with above annotations and see if it helps.

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

@jelel-fliss created a new cluster with cert-manager 1.6.0 and ingress controller 1.0.5. Right now I see the below thing in the cluster: NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE devops17...

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

@jelel-fliss logs for ing,cert-manager pods,acme pod, nginx controller is a huge file, can you share your email id I will share the logs

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

Now,I see a different error. cert-manager/controller/challenges "msg"="propagation check failed" "error"="failed to perform self check GET request 'http://devops17.nasty.orbitbi.com/.well-known/acme-challenge/Qbso0LFq4LbjK_YUV7Rtyvpon7a6I_NIESsLjd_AfJc': Get \"http://devops17.nasty.orbitbi.com/.well-known/acme-challenge/Qbso0LFq4LbjK_YUV7Rtyvpon7a6I_NIESsLjd_AfJc\": dial tcp: lookup devops17.nasty.orbitbi.com on 10.96.5.5:53: no such host" "dnsName"="devops17.nasty.orbitbi.com" "resource_kind"="Challenge"...

Kubernetes 1.22 Challenge stuck at pending : Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'

Issue resolved after pods started resolving the fqdn for what ever domain the certificate needs to be issued, we earlier had a setup in oracle cloud OCI where we wanted...

Use the new kind AlertmanagerConfig to configure alertmanager

can we use multiple receivers in alertmanagerconfig

API error (404): Could not find the file /opt/dockerslim/artifacts/creport.json in container

I have the below error when trying to slim the image, the actual image size is 4.24GB. Below are commands I used to build and slim the images respectively ```docker...