From bd00fc95abb52f0617231cec0c6ee72e74f765db Mon Sep 17 00:00:00 2001 From: rickbrouwer Date: Tue, 26 Nov 2024 19:29:34 +0100 Subject: [PATCH] Deprecate Stan scaler (#1503) Signed-off-by: rickbrouwer Signed-off-by: krishna sindhur --- content/docs/2.17/operate/security.md | 5 +++++ content/docs/2.17/scalers/nats-streaming.md | 7 ++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/content/docs/2.17/operate/security.md b/content/docs/2.17/operate/security.md index fa93994b0..74e38b142 100644 --- a/content/docs/2.17/operate/security.md +++ b/content/docs/2.17/operate/security.md @@ -20,6 +20,11 @@ While this is a good starting point, some end-users may want to use their own ce Certificates generation in the KEDA operator can be disabled by removing the console argument `--enable-cert-rotation=true` or setting it to `false`. Once this setting is disabled, user given certs can be placed in the secret `kedaorg-certs` which is automatically mounted in all the components or they can be patched to use other secret (this can be done throught helm values too). +Additionally, KEDA includes a new `--enable-webhook-patching` flag, which controls whether the operator patches webhook resources. By default, this is set to `true`, ensuring Kubernetes trusts the operator's CA. However, if webhooks are disabled or not needed in your deployment, you can set this flag to `false` to avoid errors related to missing webhook resources. + +Example use case: +- When using operator-managed certificates but disabling webhooks, set `--enable-webhook-patching=false` to prevent the operator from attempting to patch non-existent webhook resources. + All components inspect the folder `/certs` for any certificates inside it. Argument `--cert-dir` can be used to specify another folder to be used as a source for certificates, this argument can be patched in the manifests or using Helm values. Because these certificates are also used for internal communication between KEDA components, the CA is also required to be registered as a trusted CA inside KEDA components. ## Register your own CA in KEDA Operator Trusted Store diff --git a/content/docs/2.17/scalers/nats-streaming.md b/content/docs/2.17/scalers/nats-streaming.md index 490082ed3..353d987d1 100644 --- a/content/docs/2.17/scalers/nats-streaming.md +++ b/content/docs/2.17/scalers/nats-streaming.md @@ -7,6 +7,11 @@ description = "Scale applications based on NATS Streaming." go_file = "stan_scaler" +++ +> **Notice:** +> The Stan scaler (NATS Streaming) is DEPRECATED and will be removed in v2.19 - Use scaler [nats-jetstream](./nats-jetstream.md) instead. +> See also the deprecation notice [here](https://nats-io.gitbook.io/legacy-nats-docs/nats-streaming-server-aka-stan). + + ### Trigger Specification This specification describes the `stan` trigger for NATS Streaming. @@ -174,4 +179,4 @@ spec: useHttps: "true" authenticationRef: name: keda-trigger-auth-stan-secret -``` \ No newline at end of file +```