Closed StevenCaswellVR closed 3 years ago
Hi @StevenCaswellVR ,
Do you still experience this issue? I just tried to replicate it and works just fine for me
❯ helm repo list |grep kube2iam
kube2iam https://jtblin.github.io/kube2iam/
✗ helm install issue-305 kube2iam/kube2iam
NAME: issue-305
LAST DEPLOYED: Thu Apr 8 16:44:52 2021
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
To verify that kube2iam has started, run:
kubectl --namespace=default get pods -l "app.kubernetes.io/name=kube2iam,app.kubernetes.io/instance=issue-305"
Add an iam.amazonaws.com/role annotation to your pods with the role you want them to assume.
https://github.com/jtblin/kube2iam#kubernetes-annotation
Use `curl` to verify the pod's role from within:
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/
marius in xyz in ⛵ eks-testing in ~
❯ helm ls
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
issue-305 default 1 2021-04-08 16:44:52.864952 +0300 EEST deployed kube2iam-2.6.0 0.10.9
marius in xyz in ⛵ eks-testing in ~
❯ k get po
NAME READY STATUS RESTARTS AGE
issue-305-kube2iam-2p2pl 1/1 Running 0 21s
issue-305-kube2iam-hwwbg 1/1 Running 0 21s
issue-305-kube2iam-j6wqw 1/1 Running 0 21s
I still don't know what happened, but the helm repository seems to be working now. I didn't change anything on my side, but I have to believe it was something on our end and not with the project. I appreciate you looking at this and I apologize for the false alarm.
I was able to use helm to install this chart on 06-apr-2021. As of the morning of 07-apr-2021 the url returns 404.