Upgrading the Chart You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like...

          - name: istio-token
            mountPath: /var/run/secrets/tokens
            readOnly: true
          {{- if .Values.global.mountMtlsCerts }}
          # Use the key and cert mounted to /etc/certs/ for the in-cluster mTLS communications.
          - name: istio-certs
            mountPath: /etc/certs
            readOnly: true
          {{- end }}
          - mountPath: /var/lib/istio/data
            name: istio-data

      - name: Run Checks
        run: ./gradlew test -Dokhttp.platform=bouncycastle

  testcorretto:
    runs-on: ubuntu-latest
    # TODO add master build after fixing all tests in CI
    if: contains(github.event.pull_request.labels.*.name, 'providers')

    steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

// Copyright 2019 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

#include "../../../../../runtime/textflag.h"

TEXT asmtest(SB),DUPOK|NOSPLIT,$0
start:
	// Unprivileged ISA

	// 2.4: Integer Computational Instructions

	ADDI	$2047, X5				// 9382f27f
	ADDI	$-2048, X5				// 93820280
	ADDI	$2048, X5				// 9382024093820240

      name: istio-envoy
    - mountPath: /var/run/secrets/tokens
      name: istio-token
    {{- if .Values.global.mountMtlsCerts }}
    # Use the key and cert mounted to /etc/certs/ for the in-cluster mTLS communications.
    - mountPath: /etc/certs/
      name: istio-certs
      readOnly: true
    {{- end }}
    - name: istio-podinfo
      mountPath: /etc/istio/pod

      name: istio-envoy
    - mountPath: /var/run/secrets/tokens
      name: istio-token
    {{- if .Values.global.mountMtlsCerts }}
    # Use the key and cert mounted to /etc/certs/ for the in-cluster mTLS communications.
    - mountPath: /etc/certs/
      name: istio-certs
      readOnly: true
    {{- end }}
    - name: istio-podinfo
      mountPath: /etc/istio/pod

    #
    # Then starting a pod with the `inject.istio.io/templates: hello` annotation, will result in the pod
    # being injected with the hello=world labels.
    # This is intended for advanced configuration only; most users should use the built in template
    templates: {}
    # Default templates specifies a set of default templates that are used in sidecar injection.

    title: Instrument a FastAPI service adding tracing with OpenTelemetry and send/show traces in Grafana Tempo
  - author: Mikhail Rozhkov, Elena Samuylova
    author_link: https://www.linkedin.com/in/mnrozhkov/
    link: https://www.evidentlyai.com/blog/fastapi-tutorial
    title: ML serving and monitoring with FastAPI and Evidently
  - author: Visual Studio Code Team
    author_link: https://code.visualstudio.com/

    #
    # Then starting a pod with the `inject.istio.io/templates: hello` annotation, will result in the pod
    # being injected with the hello=world labels.
    # This is intended for advanced configuration only; most users should use the built in template
    templates: {}

    # Default templates specifies a set of default templates that are used in sidecar injection.

Upgrading the Chart You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like...