Cacert entries ignored for certresolver

Hitting a rate limit with all ACME providers:

time="2021-12-14T17:49:21Z" level=error msg="Unable to obtain ACME certificate for domains \"***.org\": cannot get ACME client acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-acct :: urn:ietf:params:acme:error:rateLimited :: Error creating new account :: too many registrations for this IP: see https://letsencrypt.org/docs/rate-limits/" providerName=staging.acme routerName=***.org@kubernetes rule="Host(`***.org`) && PathPrefix(`/`)"

However, this is against many certresolvers with their own caserver entries:

            - >-
              --certificatesresolvers.buypass.acme.tlschallenge=true
              --certificatesresolvers.buypass.acme.httpchallenge.entryPoint=web
              --certificatesresolvers.buypass.acme.email=sysad@efi.org
              --certificatesresolvers.buypass.acme.storage=/data/buypass.json
              --certificatesresolvers.buypass.acme.caserver=https://api.buypass.com/acme/directory
            - >-
              --certificatesresolvers.zerossl.acme.tlschallenge=true
              --certificatesresolvers.zerossl.acme.httpchallenge.entryPoint=web
              --certificatesresolvers.zerossl.acme.email=sysad@efi.org
              --certificatesresolvers.zerossl.acme.eab.kid=***
              --certificatesresolvers.zerossl.acme.eab.hmacencoded=***
              --certificatesresolvers.zerossl.acme.storage=/data/zerossl.json
              --certificatesresolvers.zerossl.acme.caserver=https://acme.zerossl.com/v2/DV90
            - >-
              --certificatesresolvers.staging.acme.tlschallenge=true
              --certificatesresolvers.staging.acme.email=sysad@efi.org
              --certificatesresolvers.staging.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory
              --certificatesresolvers.staging.acme.storage=/data/staging.json
            - >-
              --certificatesresolvers.efi.acme.tlschallenge=true
              --certificatesresolvers.efi.acme.email=sysad@efi.org
              --certificatesresolvers.efi.acme.storage=/data/acme.json

Why am I getting an error on https://acme-v02.api.letsencrypt.org/acme/new-acct when I am using https://acme-staging-v02.api.letsencrypt.org/directory as my caserver?

noticed that upon startup, the configuration is loaded as:

"certificatesResolvers": {
    "buypass": {
      "acme": {
        "caServer": "https://acme-v02.api.letsencrypt.org/directory",
        "storage": "acme.json",
        "keyType": "RSA4096"
      }
    },
    "efi": {
      "acme": {
        "caServer": "https://acme-v02.api.letsencrypt.org/directory",
        "storage": "acme.json",
        "keyType": "RSA4096"
      }
    },
    "staging": {
      "acme": {
        "caServer": "https://acme-v02.api.letsencrypt.org/directory",
        "storage": "acme.json",
        "keyType": "RSA4096"
      }
    },
    "zerossl": {
      "acme": {
        "caServer": "https://acme-v02.api.letsencrypt.org/directory",
        "storage": "acme.json",
        "keyType": "RSA4096"
      }
    }
  }