concourse / concourse/docker-image-resource
Is IMDS v2 or IRSA supported?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
I need to force the usage of Instance Metadata Service v2 for my EKS nodes in AWS. With v1 docker-image-resource is able to pull images from ECR with the instance role. With v2 docker-image-resource seems not be able to use the instance role.
A other solution is to use IAM roles for service accounts (IRSA) in AWS. But this also does not work.
resource_types:
- name: example
type: docker-image
source:
repository: <account_id>.dkr.ecr.eu-central-1.amazonaws.com/<repository_name>
tag: 0.0.1
Error messages:
IMDS v2: ...credentials not found in native keychain...
IRSA: ...401 not authorized...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided docker-image resource configuration on EKS with IMDS v2 and with IRSA, using the reported credential and authorization errors as checkpoints. Done means the resource can authenticate to ECR and pull the image through the supported AWS credential path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100