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

Feature/5514 - Add SecretRef support for venafi TPP issuer CA Bundle #7036

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sankalp-at-gh
Copy link

Pull Request Motivation

To address issue #5514 so that we would no longer need to pass long CA Bundles but could just have a reference to a secret or configmap having the bundle. Having support for secret ref will also allow reading CAs distributed by trust-manager

As per below example, any of one of the fields caBundle or caBundleSecretRef would be supported to read the CA bundle

spec:
  venafi:
    tpp:
      caBundle: <B64_ENCODED_STRING>
      caBundleSecretRef:
        name: <>
        key: <>
      credentialsRef:
        name: tpp-token
      url: https://my-server.com/vedsdk/
    zone: Certificates\public

All of the controllers, testcases and rbac have been updated to support this functionality

Kind

feature

Release Note

Add SecretRef support for venafi TPP issuer CA Bundle

Signed-off-by: Sankalp Yengaldas <sankalp.yb@fmr.com>
Signed-off-by: Sankalp Yengaldas <sankalp.yb@fmr.com>
@cert-manager-prow cert-manager-prow bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. area/api Indicates a PR directly modifies the 'pkg/apis' directory area/deploy Indicates a PR modifies deployment configuration labels May 16, 2024
@cert-manager-prow
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign wallrj for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cert-manager-prow cert-manager-prow bot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 16, 2024
@cert-manager-prow
Copy link
Contributor

Hi @sankalp-at-gh. Thanks for your PR.

I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cert-manager-prow cert-manager-prow bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label May 16, 2024
Copy link
Member

@hawksight hawksight left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR, it looks really good. Looking through from a very inexperienced view it looks quite complete but I will ask someone with the right experience to give it a. more thorough review.

It looks great though and such a great improvement to have,.

@sankalp-at-gh
Copy link
Author

Thanks for the quick review 🙂
Sure, I'll wait for a thorough review and comments if any

@sankalp-at-gh
Copy link
Author

sankalp-at-gh commented Jun 10, 2024

Hi @erikgb !

When you get some time, could you please review this PR as discussed in slack. It has been quiet some time since the PR and I hope the changes have not diverged much.
Thanks ! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Indicates a PR directly modifies the 'pkg/apis' directory area/deploy Indicates a PR modifies deployment configuration dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants