use Helm to init rustfs in sandbox

[BarryWu0812]

Tracking issue

Closes #7209

Why are the changes needed?

According to rustfs doc, we can run it with helm chart instead of scripting the yaml on our own.
We run an init container to create default bucket now because rustfs do not support default bucket config now. After migrating to helmchart, we can run a k8s post-install Job to create default bucket.

What changes were proposed in this pull request?

Use Helm to init rustfs in sandbox and run k8s post-install Job to create default bucket.

How was this patch tested?

Run make sandbox-build.
Run an example workflow and make sure the result is success.

Labels

Please add one or more of the following labels to categorize your PR:

• added: For new features.
• changed: For changes in existing functionality.
• deprecated: For soon-to-be-removed features.
• removed: For features being removed.
• fixed: For any bug fixed.
• security: In case of vulnerabilities

This is important to improve the readability of release notes.

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Docs link

• main
  • Flyte 2: Cut over to Flyte 2 new backend implementation #6583
    • use Helm to init rustfs in sandbox 👈

[popojk]

Overall looks good, thanks! Left a few comments, PTAL

[popojk]

Hey @BarryWu0812 .

1. I still saw a rustfs init pod created on routine basis, could you please check it?
2. Please rebase this PR after 1st item resolved

[pingsutw]

Could we add new path (/rustfs) to the ingress rules for the rustfs console and make sure it’s accessible from the browser?

flyte/charts/flyte-devbox/templates/proxy/ingress.yaml

Lines 38 to 55 in 61a555c

	kind: Ingress
	metadata:
	name: flyte-console
	namespace: {{ .Release.Namespace | quote }}
	labels: {{- include "flyte-devbox.labels" . | nindent 4 }}
	spec:
	rules:
	- http:
	paths:
	- path: /v2
	pathType: Prefix
	backend:
	service:
	name: flyte-console
	port:
	number: 80
	{{- end }}
	---

[pingsutw]

Could we add a patch to complete/dev kustomization.yaml to add an init container to the rustfs deployment, so that we don't need to add docker.io/minio/mc:latest and another k8s job into the devbox

- patch: |-
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: rustfs
      namespace: flyte
    spec:
      template:
        spec:
          initContainers:
          - name: create-default-buckets
            image: busybox:stable
            imagePullPolicy: IfNotPresent
            command:
            - sh
            - -c
            - mkdir -p /data/flyte-data
            securityContext:
              allowPrivilegeEscalation: false
              capabilities:
                drop:
                - ALL
              readOnlyRootFilesystem: true
              runAsNonRoot: true
            volumeMounts:
            - mountPath: /data
              name: data

[BarryWu0812]

Hi @popojk @pingsutw , I have create new PR based on main branch. Please help me to review. Thanks.