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

EKSA Curated Packages Controller Logs: cronjobs.batch "cron-ecr-renew" not found #929

Open
nrajb opened this issue Apr 27, 2023 · 1 comment

Comments

@nrajb
Copy link

nrajb commented Apr 27, 2023

What happened:
Seems starting from eks anywhere version: 0.15.x credential-provider-package is being used as default to authenticate with private Amazon Elastic Container Registry.

However in the package controller logs, right after new cluster deployment, we are still seeing references to cron-ecr-renew, which could be misleading.

Logs:

kubectl logs deploy/eks-anywhere-packages -n eksa-packages controller



2023-04-27T11:56:33.278Z	Package	installing/updating	{"chart": {"version":"0.3.9-latest-helm","registry":"","repository":"credential-provider-package","digest":"sha256:25a8a6f5b9924c3490fd717e8e5729313794235bfd64584f2c9c55fa12913bea"}}
Pulled: public.ecr.aws/eks-anywhere/credential-provider-package:0.3.9-latest-helm
Digest: sha256:25a8a6f5b9924c3490fd717e8e5729313794235bfd64584f2c9c55fa12913bea
2023-04-27T11:56:33.710Z	Package	failed to Update Secret in all namespaces	{"error": "cronjobs.batch \"cron-ecr-renew\" not found"}
2023-04-27T11:56:34.460Z	Package	creating 2 resource(s)
2023-04-27T11:56:34.727Z	Package	failed to Update Secret in all namespaces	{"error": "cronjobs.batch \"cron-ecr-renew\" not found"}
2023-04-27T11:56:34.727Z	Package	Installed	{"name": "ecr-credential-provider-package", "chart": {"version":"0.3.9-latest-helm","registry":"","repository":"credential-provider-package","digest":"sha256:25a8a6f5b9924c3490fd717e8e5729313794235bfd64584f2c9c55fa12913bea"}}

What you expected to happen:
For EKSA clusters using 0.15.x - might need to remove references to cron-ecr-renew from the controller logs since by default cronjob is not being used.

How to reproduce it (as minimally and precisely as possible):

  • Create new cluster with EKSA_AWS_x env vars
  • Right after cluster creation is completed, helm chart for curated packages will be installed
🎉 Cluster created!
--------------------------------------------------------------------------------------
The Amazon EKS Anywhere Curated Packages are only available to customers with the
Amazon EKS Anywhere Enterprise Subscription
--------------------------------------------------------------------------------------
Enabling curated packages on the cluster
Installing helm chart on cluster	
{
    "chart": "eks-anywhere-packages-eksa-poc-wl",
    "version": "0.3.9-eks-a-36"
}

  • Check package controller logs with:
    kubectl logs deploy/eks-anywhere-packages -n eksa-packages controller

Anything else we need to know?:

Environment: Bare Metal

  • EKS Anywhere Release: 0.15.2
@TerryHowe TerryHowe transferred this issue from aws/eks-anywhere Apr 27, 2023
@TerryHowe
Copy link
Contributor

Error generated from

m.log.Error(err, "failed to Update Secret in all namespaces")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants