GithubHelp home page GithubHelp logo

Comments (4)

timothyclarke avatar timothyclarke commented on July 17, 2024 2

In terms of a "second" cluster issuer. It's typically less confusing (and easier to debug) if you keep to 1 cluster issuer but have multiple solvers eg

    solvers:
    - dns01:
        route53:
          region: __CLUSTER_REGION__
          ambient: true
      selector:
        dnsZones:
        - internal.example.com
    - dns01:
        cloudflare:
          email: __cloudflareemail__
          apiKeySecretRef:
            name: cloudflare-api-key-secret
            key: API
      selector:
        dnsZones:
        - public.example.com
    - http01:
        ingress:
          class: nginx

Aka internal.example.com is on route53, public.example.com is on cloudflare and everything else uses a http01 solver.

from terraform-kubernetes-cert-manager.

bohdantverdyi avatar bohdantverdyi commented on July 17, 2024 2

@timothyclarke Thanks for PR.

@dc232 Feature has been added.

from terraform-kubernetes-cert-manager.

bohdantverdyi avatar bohdantverdyi commented on July 17, 2024

Hey, at least you can add your additional cluster issuer.

Also you can add your own yaml for cluster issuer in module.

Variable called: cluster_issuer_yaml . Just give your own yaml of cluster issuer to this variable, and module will replace default http issuer with your yaml.

Make sure that name of new cluster issuer is not same as in module, in case when you are adding second cluster issuer.

resource "kubectl_manifest" "cloudflare_cluster_issuer" {

  validate_schema = false

  yaml_body = <<EOF
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-prod
  namespace: cert-manager
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email:  __cloudflareemail__
    privateKeySecretRef:
      name: letsencrypt-prod
    solvers:
    - selector:
        dnsNames:
        - '*.vinsonjewellers.com'
        - vinsonjewellers.com
      dns01:
        cloudflare:
          email: __cloudflareemail__
          apiKeySecretRef:
            name: cloudflare-api-key-secret
            key: API
EOF
  depends_on = [module.cert_manager]
}

Anyway good idea to implement support of dns01 issuer in this module :)

from terraform-kubernetes-cert-manager.

bohdantverdyi avatar bohdantverdyi commented on July 17, 2024

@timothyclarke Looks really good, let me check locally how it works in real life )

from terraform-kubernetes-cert-manager.

Related Issues (17)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.