From 78c462e0fded57903b479208300c4ca83edd6458 Mon Sep 17 00:00:00 2001 From: chiragkyal Date: Tue, 14 May 2024 17:05:16 +0530 Subject: [PATCH] CFE-1038: update command-line argument name for feature-gate Signed-off-by: chiragkyal --- ...te-secret-injection-for-external-certificate-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/enhancements/ingress/route-secret-injection-for-external-certificate-management.md b/enhancements/ingress/route-secret-injection-for-external-certificate-management.md index efb528b781..2615b1ed21 100644 --- a/enhancements/ingress/route-secret-injection-for-external-certificate-management.md +++ b/enhancements/ingress/route-secret-injection-for-external-certificate-management.md @@ -14,7 +14,7 @@ approvers: api-approvers: # In case of new or modified APIs or API extensions (CRDs, aggregated apiservers, webhooks, finalizers). If there is no API change, use "None" - '@joelspeed' creation-date: 2022-12-13 -last-updated: 2023-07-28 +last-updated: 2024-05-14 tracking-link: # link to the tracking ticket (for example: Jira Feature or Epic ticket) that corresponds to this enhancement - https://issues.redhat.com/browse/CM-815 --- @@ -241,7 +241,7 @@ use the default certificates only when `.spec.tls.certificate/key` or `.spec.tls are not provided. The cluster-ingress-operator will propagate the relevant Tech-Preview feature gate down to the -router. This feature gate will be added as a command-line argument called `ROUTER_EXTERNAL_CERTIFICATE` +router. This feature gate will be added as a command-line argument called `ROUTER_ENABLE_EXTERNAL_CERTIFICATE` to the router and will not be user configurable. ### Risks and Mitigations