jetstack/version-checker

does not seem to support kube2iam for ECR access

Open

#66 opened on Dec 7, 2020

View on GitHub
 (3 comments) (4 reactions) (0 assignees)Go (80 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (771 stars)
PR merge metrics
 (Avg merge 1m) (2 merged PRs in 30d)

Description

Hello,

I have a K8S cluster deployed in AWS with kubeadm. Some of my images comes from the ECR of the K8S AWS account and I wanted to use kube2iam annotation on version-checker pod to allow it to check for image tags but it does not seem to work :

version-checker pod :

apiVersion: v1
kind: Pod
metadata:
  annotations:
    enable.version-checker.io/version-checker: "true"
    iam.amazonaws.com/role: ecr-read-profile
[...]

version-checker logs :

time="2020-12-07T14:47:39Z" level=error msg="error syncing 'checkoutservice-78b576896d-9pk6z/microdemo': failed to sync pod checkoutservice-78b576896d-9pk6z/microdemo: failed to check container image \"server\": failed to get tags from remote registry for \"<AWS_ACCOUNT_ID>.dkr.ecr.eu-central-1.amazonaws.com/google-samples/microservices-demo/checkoutservice\": failed to describe images: EmptyStaticCreds: static credentials are empty, requeuing" module=controller

Does the ECR authent only work with static credentials ? Would it be possible to support kube2iam to avoid giving the pod static key and password ? Thanks

Contributor guide

Research direction
Investigate the ECR authentication logic in the version checker codebase, likely in the controller or ECR client packages. The issue reports that static credentials are used; research how to dynamically assume an IAM role via kube2iam (e.g., using AWS SDK's AssumeRole or EC2 metadata). Look for existing credential providers or the function that creates the ECR client. No linked PRs; maintainer guidance is absent.
Tech stack
gokubernetesaws
Domain
authenticationclouddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go programmingKubernetes IAMkube2iam concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50