[Feature request]: packaged snap variant of aws-iam-authenticator #631
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
What would you like to be added?
Alongside the existing publication mechanisms, the Canonical team that owns Ubuntu EKS worker nodes would like to publish a snap to a snap store (aws/aws-iam-authenticator). This can be done out of tree, but having this located as close to upstream as possible is preferred.
Why is this needed?
The Ubuntu EKS worker AMIs are optimized to only provide the absolute minimum required to start a k8s worker and join an EKS control plane. The aws-iam-authenticator is currently delivered by a debian package that is distributed through a PPA. This is built for a specific distro version (20.04/Focal), which does not provide a new enough golang version to upgrade to a more modern aws-iam-authenticator version. To avoid this maintenance concern, we are switching aws-iam-authenticator to be distributed as a snap. Packaging in a snap allows us to more easily use different versions of golang without being tied to what is in the host distro.
Anything else we need to know?
We have an existing snapcraft.yaml and have published the aws-iam-authenticator as an unlisted snap. We want to ensure this gets adequate testing alongside upstream to gate future releases before making this publicly searchable. We have confirmed this works for our initial EKS use case, but there are likely corner cases we are not adequately testing.
The text was updated successfully, but these errors were encountered: