Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: issuerRef group: "cert-manager.io" does not match CertificateRequest with no group. #419

Open
inteon opened this issue Apr 15, 2024 · 2 comments
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@inteon
Copy link
Member

inteon commented Apr 15, 2024

approver-policy does not seem to be issuerRef group defaulting aware.

eg. the following policy will not match the example certificate request

apiVersion: policy.cert-manager.io/v1alpha1
kind: CertificateRequestPolicy
metadata:
  name: selfsigned-policy
spec:
  ...
  selector:
    issuerRef:
      name: "internal-ca"
      kind: "ClusterIssuer"
      group: "cert-manager.io"
---
apiVersion: cert-manager.io/v1
kind: CertificateRequest
metadata:
  name: test123
spec:
  ...
  issuerRef:
    kind: ClusterIssuer
    name: internal-ca
@erikgb
Copy link
Contributor

erikgb commented Apr 15, 2024

We have also been hit by this. As an alternative solution, we could set the group default (cert-manager.io) in cert-manager resources. IMO this would be a cleaner solution - instead of duplicating the cert-manager group default in approver-policy.

@hawksight
Copy link
Member

Related code that @inteon mentioned in today's standup

@inteon inteon added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants