-
Notifications
You must be signed in to change notification settings - Fork 87
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
Deployment Fails to Pull Image from AWS ECR Using KSOPS with Argo CD: No Basic Auth Credentials #230
Comments
🤖 Based on the information you've provided and the context from the KSOPS repository, it seems like the issue might be related to the To resolve this, you can add the Here's an example of how to add the flag: data:
kustomize.buildOptions: --enable-alpha-plugins --enable-exec After adding the flag, you should be able to use KSOPS to manage your secrets within Argo CD. Regarding the creation and management of Kubernetes secrets, specifically docker-registry secrets, with KSOPS, you would follow the same process as for any other Kubernetes secret. You can refer to the detailed step-by-step guide provided in the context above. As for compatibility issues between KSOPS v4.3.1 and Argo CD version v2.10.1+a79e0ea, I wasn't able to find any known issues within the KSOPS repository. However, it's always a good idea to ensure you're using the latest stable versions of both tools, as this can help avoid potential compatibility issues. If the issue persists after trying these steps, could you please provide more details about your setup? Specifically, the content of your Sources
|
Just edited the post above and added the enable plugins part |
🤖 It's great to hear that your ArgoCD is working well with the
|
Hi @LeoAnt02 the error ERROR: Failed to pull image "*****.dkr.ecr.us-east-2.amazonaws.com/*****:latest": no basic auth credentials suggests that the Hope this helps! This is not related to the KSOPS library itself. |
Hey @devstein Thanks for taking the time on this What would be the best solution for this ? Im still new to k8 |
The naive fix is the give the Argo CD credentials permission to pull the image from ECR Can you share the rendered deployment manifest? Maybe there are some clues based on how the patch is getting applied. |
@devstein so not sure how I can do the first fix you mentionned Here's the argo deployment manifest after the patch
|
Hello,
I'm experiencing an issue with deploying a Kubernetes application using Argo CD, where the deployment fails to pull an image from AWS ECR. The error indicates a lack of basic auth credentials, despite the secret being seemingly correctly set up via KSOPS.
Not sure if this is a bug, or I'm missing something
Any idea ?
Environment:
Argo CD Version:
v2.10.1+a79e0ea
kustomize
v5.2.1 2023-10-19T20:13:51Z
Platform
linux/arm64
kubectl
v0.26.11
KSOPS Version: 4.3.1
Issue Description:
When creating the image pull secret manually via the Kubernetes CLI, everything works as expected. However, when attempting to use KSOPS to manage the secret within Argo CD, the secret
pull-staging
does not appear to be present or correctly applied, leading to image pull failures.Steps to Reproduce:
And argoCD pod deploy successfully
pull-staging.dec.yml:
looks like this
generator.yml:
kustomization.yml:
Deployment.yml
Error on argoCD pod :
ERROR: Failed to pull image "*****.dkr.ecr.us-east-2.amazonaws.com/*****:latest": no basic auth credentials
My argocd has been patched with this
and config map to enable the --enable-alpha-plugins --enable-exec
and my aws secret are present and created correctly
The text was updated successfully, but these errors were encountered: