04/22/2020, 11:36 AM
Hi! After 2.0 update i'm having troubles managing AWS named profiles. Since in new versions eks cluster access is controlled with a named profile (that's a great thing!). Problem is, that in development env I have a named profile and in CI/CD [github action] a default one. When updating from dev machine profile name is stored in the resource description and CICD pipeline is fails, because it's on a default profile. One of the solutions i'm thinking about is to write ~/.aws/credentials on CICD that has a same profile, but that seams like doing something wrong.. am I missing something here, is there some config variable to allow eks access on a default profile in a github action?


04/22/2020, 3:29 PM
hey! How do you currently switch profiles? Is it possible to just set the
env var?


04/23/2020, 4:44 PM
thanks! i've changed my local setup to use a default profile, i'll need to check again if specifying env profile overrides kubeconfig settings. i'll post here once i have some results.