Nexus3: Unable to import custom CAs about helm-charts

[stevehipwell]

@Jasper-Ben do you want to try the latest release?

[stevehipwell]

Could you try again?

[Jasper-Ben]

@stevehipwell Nice! That seems to have done the trick on the CA front. However, now I'm back to LDAP issues... I assume groupIdAttribute should not fail, as I have mapGroupAsRolesType set to "dynamic"?

P.S.: I am going to move this into a new issue.

P.P.S.: Nevermind, I had an error in my LDAP config. works now 👍

Thanks a lot for your help!

[stevehipwell]

@Jasper-Ben could you show what values you're using and the structure of the secret?

[Jasper-Ben]

Hi @stevehipwell,
the secret looks like this:

Name:         ca-certs
Namespace:    nexus3
Labels:       <none>
Annotations:  <none>

Type:  Opaque

Data
====
legacy-rsa-ca:  1773 bytes
secure-es-ca:   1314 bytes
secure-rsa-ca:  2464 bytes

The data is created from PEM CA files:

[jasper@pc-891 nexus3]$ file secure-rsa-ca.crt 
secure-rsa-ca.crt: PEM certificate

Created from within terraform:

resource "kubernetes_secret" "ca-certs" {
    metadata {
        name        = "ca-certs"
        namespace   = rancher2_namespace.nexus3.id
    }
    data = {
        "legacy-rsa-ca" = "${file("${path.module}/legacy-rsa-ca.crt")}"
        "secure-rsa-ca" = "${file("${path.module}/secure-rsa-ca.crt")}"
        "secure-es-ca"  = "${file("${path.module}/secure-ec-ca.crt")}"
    }
}

[stevehipwell]

@Jasper-Ben could you add the full logs from the ca-certs init container? I suspect it's something to do with the file system bug that I fixed and can probably be fixed by swapping the init container order.

[Jasper-Ben]

@stevehipwell the ca-certs container's log only contains

Certificate was added to keystore 
Certificate was added to keystore 
Certificate was added to keystore 

[Jasper-Ben]

@stevehipwell Unfortunately still errors 😞

[Jasper-Ben]

just in case: here is my current values.yml. Hope it helps