Skip to content

Is the ignore of spec.tls.caCertificate on purpose ? #115

@strima

Description

@strima

As far as i can see in the code the spec.tls.caCertificate on the route object is nowhere considered to be set

  • Is this on purpose ?
    • If yes, then how is this intended to be populated ?
    • If yes, would it make sense to add a short note regarding the intended setting of that in the documentation ?
  • If no, how could a suitable PR look like
    • Since cert-manager populates the secret with the necessary additional ca certs i would have taken them from there and use that as value(s) for the spec.tls.caCertificate field

Looking forward to the answers

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions