Error: failed calling webhook: http: server gave HTTP response to ?HTTPS client

[pietergmail]

What happened?

When i try to create a simple certmanager in my cluster i get this error:
I0409 14:24:04.103906 1 api.go:119] "Not ready" logger="cert-manager.checkAPI" err="Internal error occurred: failed calling webhook \"webhook.cert-manager.io\": failed to call webhook: Post \"https://cert-manager-7a81ea29-webhook.cert-manager.svc:443/validate?timeout=30s\": http: server gave HTTP response to HTTPS client"

Example

// Create cert-manager into our cluster
export function createCertManager(){
  return new certmanager.CertManager("cert-manager", {
  installCRDs: true,
  helmOptions: {
      namespace: "cert-manager",
      name: "cert-manager",
      createNamespace: true,
      disableWebhooks: false,

    },
  });
}

Output of pulumi about

CLI
Version 3.111.1
Go Version go1.22.1
Go Compiler gc

Plugins
NAME VERSION
aws 6.27.0
azapi 1.11.0
azure-native 2.30.0
kubernetes 4.8.1
nodejs unknown
tls 5.0.1

Host
OS ubuntu
Version 22.04
Arch x86_64

This project is written in nodejs: executable='/usr/bin/node' version='v20.11.1'

Current Stack: pietergmail/infrastructure-Azure-Pulumi-V2/temp-env

.....
(private info)
......

Found no pending operations associated with temp-env

Backend
Name pulumi.com
URL https://app.pulumi.com/pietergmail
User pietergmail
Organizations pietergmail
Token type personal

Dependencies:
NAME VERSION
@types/node 18.19.21
@typescript-eslint/eslint-plugin 6.21.0
eslint-config-prettier 9.1.0
typescript 5.4.2
@ediri/azapi 1.11.0
@pulumi/pulumi 3.111.1
@pulumi/tls 5.0.1
eslint-plugin-promise 6.1.1
eslint-plugin-import 2.29.1
eslint-plugin-n 16.6.2
@pulumi/aws 6.27.0
@pulumi/kubernetes 4.8.1
eslint-config-standard-with-typescript 43.0.1
@pulumi/azure-native 2.30.0
eslint 8.57.0

Pulumi locates its logs in /tmp by default

Additional context

I am creating the cluster on azure AKS

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).