enum:
                          - INVALID
                          - MERGE
                          - ADD
                          - REMOVE
                          - INSERT_BEFORE
                          - INSERT_AFTER
                          - INSERT_FIRST
                          - REPLACE

                          enum:
                          - INVALID
                          - MERGE
                          - ADD
                          - REMOVE
                          - INSERT_BEFORE
                          - INSERT_AFTER
                          - INSERT_FIRST
                          - REPLACE

properties: operation: description: Operation controls whether or not to update/add a tag, or to remove it. enum: - UPSERT - REMOVE type: string value: description: Value is only considered if the operation is `UPSERT`. type: string type: object x-kubernetes-validations: - message: value must be set when operation is UPSERT rule: '((has(self.operation) ? self.operation : '''') == ''UPSERT'') ? self.value != '''' : true' - message: value must not be set when operation is REMOVE rule: '((has(self.operation)...

1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
We can then merge the profile onto the defaults, then the user settings onto that.

1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
We can then merge the profile onto the defaults, then the user settings onto that.

1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
We can then merge the profile onto the defaults, then the user settings onto that.

1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
We can then merge the profile onto the defaults, then the user settings onto that.

    prometheus.io/scrape: "true"
    prometheus.io/path: "/stats/prometheus"
    inject.istio.io/templates: "gateway"
    sidecar.istio.io/inject: "true"

  # Define the security context for the pod.
  # If unset, this will be automatically set to the minimum privileges required to bind to port 80 and 443.
  # On Kubernetes 1.22+, this only requires the `net.ipv4.ip_unprivileged_port_start` sysctl.
  securityContext: ~

lk.com us.ax us.com us.eu.org us.gov.pl us.in us.kg us.na us.org us.platform.sh us.reclaim.cloud usa.museum usa.oita.jp usantiques.museum usarts.museum uscountryestate.museum usculture.museum usdecorativearts.museum user.aseinet.ne.jp user.party.eus user.srcf.net usercontent.jp users.scale.virtualcloud.com.br usgarden.museum ushiku.ibaraki.jp ushistory.museum ushuaia.museum uslivinghistory.museum usr.cloud.muni.cz ustka.pl usui.fukuoka.jp usuki.oita.jp ut.us utah.museum utashinai.hokkaido.jp utazas.hu...

1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
We can then merge the profile onto the defaults, then the user settings onto that.