-
Notifications
You must be signed in to change notification settings - Fork 191
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
[OCIRepository] GCP Artifact Registry Auth - Helm OCI 403 error #798
Comments
Hi, OCI HelmRepository doesn't support auto-login at the moment. It's planned to be added in the future, but at the moment, you have to pass credentials in a secret reference as shows in https://fluxcd.io/docs/components/source/helmrepositories/#basic-access-authentication. The reason HelmRepository status shows Ready is because if no secret is provided, it doesn't know if it needs to perform a registry login. Only the HelmChart performs pull operation. HelmRepository performs login only if a secret is provided. HelmChart uses the secret provided in the HelmRepository. |
Thank you for the information. |
There's on going work to extract that code from image-reflector and use it in other projects. It's being tracked in fluxcd/image-reflector-controller#264 . |
Got it, thanks @darkowlzz Also, temp resolution to this was to construct docker credentials like:
Then for the HelmRelease:
|
Hello,
I am not sure what am I doing wrong but following error message is received:
Versions:
Config in flux:
HelmRepository
HelmRelease
Status shows ok:
Workload identity service account attached to
kustomize-controller
,source-controller
andimage-reflector-controller
all haveroles/artifactregistry.reader
attached to them inartifact-registry-project
, where GKE itself is deployed in separated project.GCP Audit log shows:
While manual listing works:
Attaching same service-accounts in k8s to
google/cloud-sdk
pod allows listing and accessing the registry.The text was updated successfully, but these errors were encountered: