Closed piyush94 closed 4 years ago
EKS example: from creds: aws --profile default configure set aws_access_key_id "my-20-digit-id" aws --profile default configure set aws_secret_access_key "my-40-digit-secret-key"
from attrs: aws eks --region "region-code" update-kubeconfig --name "cluster_name" “optional flags”
@piyush94 Should we install aws-cli version 2.0? Right now we are on 1.7?
@sbtaylor15 Sure, should be fine.
AWS Variables
AWS Commands Run
Azure Variables
Azure Commands Run
@sbtaylor15 Thanks! Both EKS and AKS deployments are working. There is a typo "servicepricipal" in the helm script that needs to be fixed.
Also, we would definitely need the login variables to be coming from credentials and also hidden in the log and subsequent override values. These additions currently seem to be missing from proxy image.
@piyush94 Pull deployhub-rproxy:master to get the latest proxy that includes the changes. We will re-tag to latest once the credentials have been hidden.
Hi, As aws and azure cli are part of deployhub, is it possible to have support for deploying helm charts into, EKS and AKS respectively using credentials. So that deployhub can configure the cluster locally temporarily and deploy the helm charts.