are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console secretKey: console123 policy: consoleAdmin ## Additional Annotations for the Kubernetes Job makeUserJob makeUserJob: podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup:...

- Introduce a feature gate `DisableCloudProviders` allowing to disable cloud-provider initialization in KAPI, KCM and kubelet.

           * fails the `ScheduledFuture`, which might be visible only to users who operate directly
           * on the delegate executor's queue.
           *
           * (Users who try to operate directly on the `ScheduledFuture` may have additional
           * problems. For example, if they cancel that `Future`, it won't cancel the user-visible
           * `ListenableScheduledTask`. This is essentially the same problem as the

deployment/statefulset includes checksums of secrets/config, ## So that when these change on a subsequent helm install, the deployment/statefulset ## is restarted. This can result in unnecessary restarts under GitOps tooling such as ## flux, so set to "true" to disable this behaviour. ignoreChartChecksums: false ## Additional arguments to pass to minio binary extraArgs: [] # example for enabling FTP: # - --ftp=\"address=:8021\" # - --ftp=\"passive-port-range=10000-10010\" ## Additional volumes to minio container...