documentation: Improve explanation of `kubernetes_json_patches` (#7832)

Co-authored-by: Marc 'risson' Schmitt <marc.schmitt@risson.space>
This commit is contained in:
Philipp Kolberg 2023-12-12 01:24:35 +01:00 committed by GitHub
parent f2aa83a731
commit 333d781f92
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 3 deletions

View File

@ -64,9 +64,17 @@ kubernetes_image_pull_secrets: []
# (Available with 2022.11.0+) # (Available with 2022.11.0+)
# Applies to: proxy outposts # Applies to: proxy outposts
kubernetes_ingress_class_name: null kubernetes_ingress_class_name: null
# Optionally apply an RFC 6902 compliant patch to the Kubernetes objects. This value expects # Optionally apply an RFC 6902 compliant patch to the Kubernetes objects.
# a mapping of a key which can be any of the values from `kubernetes_disabled_components`, # For an understanding of how this works, refer to the link below:
# which configures which component the patches are applied to. For example: # https://github.com/kubernetes-sigs/kustomize/blob/master/examples/jsonpatch.md
#
# This value expects a mapping where the key represents
# the Kubernetes component that shall be patched.
# It can be any of the same values supported by `kubernetes_disabled_components`.
#
# For example use this patch to add custom resource requests and limits
# to the outpost deployment:
#
# deployment: # deployment:
# - op: add # - op: add
# path: "/spec/template/spec/containers/0/resources" # path: "/spec/template/spec/containers/0/resources"