Publish helm chart to repository (eks-charts)

[joshuabaird]

Are there plans to publish the Helm chart here to any official repository like the other EKS charts over at eks-charts?

Is there any reason this chart isn't included in eks-charts?

[joshuabaird]

@nnmin-aws Should I open a PR in eks-charts to move this chart there so that it gets published to https://aws.github.io/eks-charts?

[joshuabaird]

I opened a PR here for discussion: aws/eks-charts#1123

[DhruvBundheliya]

It's better if it's added in eks-charts. Looking forward to this!!
+1

[bryantbiggs]

this should not be added to EKS charts, but instead it should be published directly from this repository to public ECR - ref aws/eks-charts#1070

[joshuabaird]

It doesn't look like this repo has any active maintainers. I think it's been forgotten about.

[yrotilio]

I believe the eks-pod-identity-agent docker image and charts should be pushed in the public ECR, like other EKS add-ons. We actually need these artifacts to be publicly available in order to replicate it and make it available to our airgaped environments.

It rather seems odd to publicly declare a feature such as eks pod identity as GA, without any apparent release management in the public repo. It feels like a lazy effort somehow..

We're pretty sad about this, because the feature in itself seems so much better than IRSA.

[dims]

@yrotilio your our airgaped environments ... they are non EKS self managed k8s clusters?

[yrotilio]

I'm sorry, I see the confusion you have from my previous message. I actually mean AWS EKS Cluster with no access to networks outside the company's private network. Calling them airgap is an overstatement considering how EKS works..

The fact is that our EKS clusters no access to public repositories, so they cannot pull the eks-pod-identity-agent from the publicly exposed ECR the chart in this repo uses, and our privately hosted internal registry cannot pull since from it either since the ECR is not in our whitelisted public repos (and I'm pretty sure that since our internal registry has no AWS identity, it will not work anyway).