From 11aac3f5dcc466b876fc589ebe116c120ace47fd Mon Sep 17 00:00:00 2001 From: = Date: Sat, 18 Jan 2025 18:58:26 +0530 Subject: [PATCH] docs: updated k8s operator template section with base64DecodeBytes content --- .../platforms/kubernetes/infisical-secret-crd.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx b/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx index f263b518a..9e01f36d9 100644 --- a/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx +++ b/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx @@ -672,6 +672,10 @@ When you set `includeAllSecrets` as `false` the Kubernetes secrets outputs will {"NEW_KEY":"LyBoZWxsbw=="} ``` +Available Template Functions + +- `base64DecodeBytes`: Converts a base64-encoded string into a byte array. This is commonly used for storing binary data in Infisical as base64 and syncing it with the operator. However, Kubernetes also performs base64 encoding, leading to double base64 conversion. To avoid this, you can decode the base64 string just before saving it to the operator. + Creation polices allow you to control whether or not owner references should be added to the managed Kubernetes secret that is generated by the Infisical operator. @@ -960,4 +964,5 @@ metadata: type: Opaque ``` - \ No newline at end of file + +