Skip to content

Commit

Permalink
Fixed confusing part of the docs regarding how kube context should be…
Browse files Browse the repository at this point in the history
… supplied
  • Loading branch information
koslib committed Oct 14, 2022
1 parent 6c6edcc commit 35c8b85
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,11 +81,13 @@ Use the output of your command in later steps

```



# Accessing your cluster

> Breaking change from v2.x and onwards
This action does not require any kube-config data set as a secret to connect to the repo. Instead, by authenticating with your AWS account, it automatically generates a kube-config file for your cluster which is then used to execute any `helm` commands.

From version v2.x and onwards, this action does not require any kube-config data set as a secret to connect to the repo. Instead, by authenticating with your AWS account, it automatically generates a kube-config file for your cluster which is then used to execute any `helm` commands.
However if you find this configuration option complicated, you can still supply `KUBE_CONFIG_DATA` as a repository secret, however this is not endorsed by this repository.


# Contributions
Expand Down

0 comments on commit 35c8b85

Please sign in to comment.