Updated readme to emphasize that we need kubeconfig contents, not path
This commit is contained in:
parent
8693d6fcb7
commit
91cd4e7064
@ -26,7 +26,7 @@ In both these approaches it is recommended to store these contents (kubeconfig f
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>kubeconfig</code><br/>Kubectl config</td>
|
||||
<td>(Relevant for kubeconfig approach) Configuration file to be used with kubectl</td>
|
||||
<td>(Relevant for kubeconfig approach) Contents of the configuration file to be used with kubectl (e.g. can be pulled from a secret)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>context</code><br/>Context</td>
|
||||
@ -55,6 +55,8 @@ In both these approaches it is recommended to store these contents (kubeconfig f
|
||||
id: setcontext
|
||||
```
|
||||
|
||||
**Please note** that the input requires the _contents_ of the kubeconfig file, and not its path.
|
||||
|
||||
Following are the ways to fetch kubeconfig file onto your local development machine so that the same can be used in the action input shown above:
|
||||
|
||||
#### For Azure Kubernetes Service cluster
|
||||
|
@ -7,7 +7,7 @@ inputs:
|
||||
required: true
|
||||
default: 'kubeconfig'
|
||||
kubeconfig:
|
||||
description: 'Kubernetes Config'
|
||||
description: 'Contents of kubeconfig file'
|
||||
required: false
|
||||
default: ''
|
||||
context:
|
||||
|
Loading…
x
Reference in New Issue
Block a user