You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting .spec.provider to aws is mandatory when using OIDC and IRSA for allowing the pods to talk to ECR using a role. Failing to add this provider to the Helm Repository manifest will make the Source Controller receive 401 error from AWS when trying to downoad the Helm artifact even when using the correct role and policy. The documentation states that it is optional but in the next prapgraph, it details how to attach a role to the source-controller service account so that it can pull charts from ECR which won't happen without correctly setting the provider.
The text was updated successfully, but these errors were encountered:
Setting
.spec.provider
toaws
is mandatory when using OIDC and IRSA for allowing the pods to talk to ECR using a role. Failing to add this provider to the Helm Repository manifest will make the Source Controller receive 401 error from AWS when trying to downoad the Helm artifact even when using the correct role and policy. The documentation states that it is optional but in the next prapgraph, it details how to attach a role to the source-controller service account so that it can pull charts from ECR which won't happen without correctly setting the provider.The text was updated successfully, but these errors were encountered: