Juan Ariza Toledano

Hi @robinliubin I was unable to reproduce the issue using the **values.yaml** below: ```yaml defaultBuckets: "test" provisioning: enabled: true policies: - name: test statements: - effect: "Allow" actions: ["s3:*"] resources:...

Hi @robinliubin I'm also enabling persistence in my tests (it's enabled by default). Why did you change the default mount path (see https://github.com/bitnami/charts/blob/main/bitnami/minio/values.yaml#L1012)? Please note it was replaced at https://github.com/bitnami/charts/commit/e707712fbd687ac271fdcecdf415f4f2a6aeb76e

Hi @robinliubin The new container image expects the data to be mounted on a different path, see value for `MINIO_DATA_DIR`: - https://github.com/bitnami/containers/tree/main/bitnami/minio#customizable-environment-variables Therefore, the mount path must be aligned with...

Hi @daroga0002 Please check my approach for using a statefulset at https://github.com/bitnami/charts/pull/23904

@daroga0002 using a statefulset doesn't imply that Flink cluster isn't dynamic nor stateful. The solution I'm proposing combining statefulset's with headless services' capabilities provide you a solution for the registering...

Thanks for your fast response. I will try with that version in the meantime. Regards, Juan

Thanks @DmitriyLewen ! I noticed you self-assigned this issue, I really appreciate it. Please don't hesitate to let me know it if you're busy to address it and you want...

Hi @knqyf263 Please note the CSAF document added to the test was created to filter out vulnerabilities affecting a container in particular (Bitnami ArgoCD 2.9.3-2 Amd64 Debian12). Therefore, it must...

> I think VEX documents should be interpreted in a context-agnostic way I can think of scenarios where VEX documents could be provided within some specific context (e.g. to express...

You're right @knqyf263 ! I was confused since I was under the impression the validity of the provided CSAF doc was questioned. That said, as you mentioned the current implementation...