Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes Agent Helm-Chart: Unable to perform helm registry login in script step #9153

Open
rain-on opened this issue Dec 2, 2024 · 0 comments
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@rain-on
Copy link

rain-on commented Dec 2, 2024

Severity

No response

Version

2.7.0+ and 1.18.2 ->2.0.0

Latest Version

None

What happened?

If a script running in the agent attempts to call helm registry login - it fails, indicating a readonly file system.

This is caused by the recent changes which mount a readonly secret at the default helm registry config location (And thus, the helm command is unable to update the file).

Reproduction

Install an affected version of the agent - the agent.upgrade.dockerAuth values do not need to be set.

Attempt to execute a script on the worker (eg via the script console). This script should perform a valid helm registry login operation.

The script will fail, with helm indicating that the filesystem is readonly.

Error and Stacktrace

No response

More Information

No response

Workaround

Prior to calling Helm registry login the environment variable HELM_REGISTRY_CONFIG can be set to an arbitrary file location (eg ~/helm_registry_config.json).
For the remainder of the step, this file will be used for tracking registry logins, rather than the default file.

@rain-on rain-on added the kind/bug This issue represents a verified problem we are committed to solving label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

1 participant