Trust-manager- implementation of the TPL function on 2 parameters

[Asif-git03]

• This pull request adds support for template configuration of app.webhook.tls.approverPolicy.certManagerNamespace and app.trust.namespace.
• These values can now be dynamically set using Helm templating, with defaults to the release namespace if not specified.

[cert-manager-prow]

Hi @Asif-git03. 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.

[Asif-git03]

Hi Team,

Request you to please review the PR, since the DCO signoff: yes

[Asif-git03]

Hi Team,

Could you please check on this PR once

[Asif-git03]

Hi Team,

Request you to please review the PR, since the DCO signoff: yes

[erikgb]

@Asif-git03 trust-manager is a community project and maintainers/reviewers all have day-time jobs. So please don't expect reviews when you request it. And no point "spamming". 😓

I am personally not in favor of your proposed changes. What is the use case? And how is it related to DRY? It definitely increases complexity by adding a second layer of templating. Trying to understand what your goal is, but no luck so far.....

[Ceddaerrix]

@Asif-git03 trust-manager is a community project and maintainers/reviewers all have day-time jobs. So please don't expect reviews when you request it. And no point "spamming". 😓

I am personally not in favor of your proposed changes. What is the use case? And how is it related to DRY? It definitely increases complexity by adding a second layer of templating. Trying to understand what your goal is, but no luck so far.....

Hello Erik (@erikgb),
I am Asif's team lead on this item. From what I see, the task of adding some DRY (Don't Repeat Yourself) support has been misunderstood.
He will rollback his changes and come back with a proper implementation...

Our intent is that, because we are using cert-manager and trust-manager into an umbrella chart, we want in our chart to default the app.trust.namespace and app.webhook.tls.approverPolicy.certManagerNamespace parameters to "{{ .Release.Namespace }}" so all the namespaces involved are in sync whatever the value of the --namespace option is. In order to do so, we need to introduce the tpl function where these 2 parameters are used in the templates.

[Asif-git03]

Hi Erik,

I have reverted the changes which were earlier done, and have made new changes which can avoid repetition of the same parameter multiple times

[erikgb]

Ok, I understand the use case better now. Thanks for explaining @Ceddaerrix! I am personally not a big fan of the proposed changes, but we will discuss this in the maintainer team.

@Asif-git03 Can you please update the PR title and description, and revert irrelevant changes in the PR diff?

[Asif-git03]

Sure Eric, how do you want it to be?(PR title and description) :)

[cert-manager-prow]

[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 sgtcodfish 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:

• OWNERS

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