repository.yaml not found if permissions on $KUBECONFIG are bad about helm-s3 HOT 3 CLOSED

• Are you using Helm v2?

  The path of the repositories.yaml file suggests that, as it should be ~/.config/helm/repositories.yaml on Linux in Helm v3.

• What is your helm-s3 plugin version?

• Also, why do you have insecure permissions on KUBECONFIG in the first place?

from helm-s3.

We are using helm3 and the newest version of the plugin.

~$ helm version
version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.21.3"}
~$ helm s3 version
0.15.1

As far as the permissions go, there was nothing sensitive in the files (no certs/passwords/etc), so it wasn't super important.
We have changed the permission on the config file and everything is working, so this is not a blocker for us.

from helm-s3.

I suppose that the warning output somehow mingles helm version detection and it is detected as v2.

In such cases helm version may be forced with HELM_S3_MODE=v3 env var.

Further, I think the plugin should stop falling back to v2 and fall back to v3 instead, as v2 is unsupported for a long time already. I made a PR #334

I'm going to close this, anyway, thanks for reporting!

from helm-s3.