Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure deployment to EKS #80

Merged
merged 1 commit into from
Nov 28, 2018

Conversation

robert-bo-davis
Copy link
Contributor

This PR adds support for EKS.

To deploy to EKS, you should have api_server and kubernetes_certificate secrets set in drone. If drone is deploying from outside of AWS, you should also have an aws_access_key_id, aws_secret_access_key secret. An AWS_DEFAULT_REGION environmental variable should also be set for the deployment.

pipeline
  helm_deploy:
    image: quay.io/ipedrazas/drone-helm
    chart: ./charts/my-chart
    release: ${DRONE_BRANCH}
    values: image.tag=${DRONE_BRANCH}-${DRONE_COMMIT_SHA:0:7}
    prefix: STAGING
    namespace: staging
    eks_cluster: my-eks-cluster
    environment:
      - AWS_DEFAULT_REGION=us-east-1

    secrets: [ aws_access_key_id, aws_secret_access_key, api_server, kubernetes_certificate ]

fixes #78

@ipedrazas
Copy link
Owner

Hey, thanks for this contribution. Could you add a quick test to verify that the new var doesn't break anything?

thanks!

@robert-bo-davis
Copy link
Contributor Author

Some very basic test have been and support for specifying a role ARN has been added. Thanks!

@ipedrazas ipedrazas merged commit c2f9210 into ipedrazas:master Nov 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

add support for EKS cluster authentication
2 participants