genSelfSignedCert cannot verify itself about sprig

[sgandon]

I am also experiencing issues with Self Signed Certificate generated with helm.
I am trying to generate certificates for the traefik ingress tcp route.
But traefik fails to accept them.
looking at a working sefl signed certificate (that succeeds the openssl verify -CAfile test as well as traefik ssl validation) it has 3 extensions

        X509v3 extensions:
            X509v3 Subject Key Identifier:
                D0:18:33:9D:9C:80:3B:00:E2:D0:F9:E5:C7:50:77:CA:2D:58:2B:10
            X509v3 Authority Key Identifier:
                keyid:D0:18:33:9D:9C:80:3B:00:E2:D0:F9:E5:C7:50:77:CA:2D:58:2B:10

Notice the same values for subject and authority key.
where certificate created by sprig do not have those extensions

       X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Basic Constraints: critical
                CA:FALSE

I don't know if this is the reason, I am no expert but this issue prevents me to use tcp ingress in Kube right now.

[MikaelSmith]

openssl/openssl#1418 is likely the root of why it doesn't work. Although I'm also in favor of this workaround.