Fix an inconsistency problems in setup of agent
@@ -77,10 +77,10 @@ helm repo update
### Validate
-You can validate that your deployment `config.yml` file is compatible with the version you are trying to deploy:
+You can validate that your deployment `config.yaml` file is compatible with the version you are trying to deploy:
```bash
-polyaxon admin deploy -f config.yml --check
+polyaxon admin deploy -f config.yaml --check
```
### Dry run
@@ -93,14 +93,14 @@ polyaxon admin deploy -f config.yaml --dry-run
### Deploy
-Now you can install Polyaxon Agent with your `config.yml` file.
+Now you can install Polyaxon Agent with your `config.yaml` file.
> **Note**: it's important to know that there's an initial delay before you can access Polyaxon API, and before some pods will turn green, which is set to 2 minutes.
You can use Polyaxon CLI to manage the deployment
```bash
-polyaxon admin deploy -f config.yml
+polyaxon admin deploy -f config.yaml
```
Or you can use Helm to do the same:
@@ -111,7 +111,7 @@ in Helm 2
helm install polyaxon/polyaxon \
--name=<RELEASE_NAME> \
--namespace=<NAMESPACE> \
- -f config.yml
+ -f config.yaml
```
in Helm 3
@@ -119,7 +119,7 @@ in Helm 3
```bash
helm install <RELEASE_NAME> polyaxon/polyaxon \
--namespace=<NAMESPACE> \
- -f config.yml
+ -f config.yaml
```
`--name` or `name` is an identifier used by helm to refer to this deployment.
@@ -136,7 +136,7 @@ we again recommend using `polyaxon` to make it always easy to remember.
helm install polyaxon/polyaxon \
--name=polyaxon \
--namespace=polyaxon \
--f config.yml
+-f config.yaml
```
>**Note**: "Release name already exists error"
@@ -165,13 +165,13 @@ the host and the ports based on these notes.
To upgrade Polyaxon to a newer version, you can simply run the following command using Polyaxon CLI:
```bash
-polyaxon admin upgrade -f config.yml
+polyaxon admin upgrade -f config.yaml
```
Or using Helm
```bash
-helm upgrade polyaxon polyaxon/polyaxon -f config.yml
+helm upgrade polyaxon polyaxon/polyaxon -f config.yaml
```
## Turn off a Polyaxon Agent
@@ -181,7 +181,7 @@ and depending on your persistence configuration you can keep all your data saved
You can also decide to completely turn off Polyaxon and remove the namespace and computational resources.
-`polyaxon admin teardown -f config.yml`
+`polyaxon admin teardown -f config.yaml`
Or
