diff --git a/README.md b/README.md index d847f99..14351e1 100644 --- a/README.md +++ b/README.md @@ -63,9 +63,9 @@ steps: drone-helm3 is largely backwards-compatible with drone-helm. There are some known differences: * You'll need to migrate the deployments in the cluster [helm-v2-to-helm-v3](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/). +* EKS is not supported. See [#5](https://github.com/pelotech/drone-helm3/issues/5) for more information. * The `prefix` setting is no longer supported. If you were relying on the `prefix` setting with `secrets: [...]`, you'll need to switch to the `from_secret` syntax. * Several settings no longer have any effect. The plugin will produce warnings if any of these are present: - * `purge` -- this is the default behavior in Helm 3 * `recreate_pods` * `tiller_ns` @@ -80,6 +80,6 @@ Since helm 3 does not require Tiller, we also recommend switching to a service a This repo is setup in a way that if you enable a personal drone server to build your fork it will build and publish your image (makes it easier to test PRs and use the image till the contributions get merged) - + * Build local ```DRONE_REPO_OWNER=josmo DRONE_REPO_NAME=drone-ecs drone exec``` -* on your server (or cloud.drone.io) just make sure you have DOCKER_USERNAME, DOCKER_PASSWORD, and PLUGIN_REPO set as secrets \ No newline at end of file +* on your server (or cloud.drone.io) just make sure you have DOCKER_USERNAME, DOCKER_PASSWORD, and PLUGIN_REPO set as secrets diff --git a/assets/kubeconfig.tpl b/assets/kubeconfig.tpl index 92ec2c7..3ed8630 100644 --- a/assets/kubeconfig.tpl +++ b/assets/kubeconfig.tpl @@ -24,16 +24,4 @@ users: user: {{- if .Token }} token: {{ .Token }} -{{- else if .EKSCluster }} - exec: - apiVersion: client.authentication.k8s.io/v1alpha1 - command: aws-iam-authenticator - args: - - "token" - - "-i" - - "{{ .EKSCluster }}" - {{- if .EKSRoleARN }} - - "-r" - - "{{ .EKSRoleARN }}" - {{- end }} {{- end }}