bottlerocket-os / bottlerocket-os/bottlerocket

Unable to pull EKS add-on images or SSM with FIPS bottlerocket images in an isolated VPC

Open
#4,372 6 comments 8 reactions 0 assignees View on GitHub
status/needs-triage type/bug
Dominant language
Rust
Stars
9.7k
Forks
586
Avg merge
1d 18h
Merged PRs (30d)
12

Description

**Image I'm using:**
bottlerocket-aws-k8s-1.31-fips-x86_64-v1.31.0-24c0647f

**What I expected to happen:**
The worker nodes will be able to pull the neccesary eks-addon images and I will be able to SSM into the worker nodes.

**What actually happened:**
The pods are unable to pull the necessary images and I am unable to SSM into the worker nodes.

**How to reproduce the problem:**
Deploy worker nodes using any FIPS enabled bottlerocket image into an isolated VPC and attempt to deploy amazon EKS add-ons or ssm into the worker nodes.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with the named FIPS Bottlerocket image in an isolated VPC, testing both EKS add-on image pulls and SSM access. No files, tests, or entry points are identified; done means determining why both capabilities fail and documenting or validating a fix for the reported environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes, linux
Domain
cloud, networking, operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.