You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diff --git a/content/en/docs/ops/configuration/mesh/secret-creation/index.md b/content/en/docs/ops/configuration/mesh/secret-creation/index.md
index 03e2b67b6..91448dc74 100644
--- a/content/en/docs/ops/configuration/mesh/secret-creation/index.md+++ b/content/en/docs/ops/configuration/mesh/secret-creation/index.md@@ -4,6 +4,10 @@ description: Describes how Citadel determines whether to create service account
weight: 30
---
+ {{< warning >}}+ This document describes the behavior of Citadel, which is not enabled by default.+ {{< /warning >}}+
When a Citadel instance notices that a `ServiceAccount` is created in a namespace, it must decide whether
it should generate an `istio.io/key-and-cert` secret for that `ServiceAccount`.
In order to make that decision, Citadel considers three inputs (note: there can be multiple Citadel instances
The text was updated successfully, but these errors were encountered:
Source File: /docs/ops/configuration/mesh/secret-creation/index.md
Diff:
The text was updated successfully, but these errors were encountered: