Remove experimental features page from v0.13 docs
Both OCI storage and HelmOps have been moved out of experimental status.
This commit is contained in:
parent
3b93de4066
commit
01fabc8732
|
|
@ -1,39 +0,0 @@
|
|||
# How to enable experimental features
|
||||
|
||||
Fleet supports experimental features that are disabled by default and that can be enabled by the user.
|
||||
|
||||
Enabling/disabling experimental features is done using extra environment variables that are available when deploying `rancher/fleet`.
|
||||
|
||||
See also "[Configure Fleet Install Options in Rancher](./ref-configuration#configure-fleet-install-options-in-rancher)".
|
||||
|
||||
## Available experimental features
|
||||
|
||||
Right now Fleet supports the following experimental features:
|
||||
|
||||
Fleet currently supports the following experimental features:
|
||||
* OCI storage: [`EXPERIMENTAL_OCI_STORAGE`](./oci-storage.md)
|
||||
* HelmOps: [`EXPERIMENTAL_HELM_OPS`](./helm-ops.md)
|
||||
|
||||
## Enabling an experimental feature
|
||||
|
||||
### Enabling when installing Fleet stand-alone
|
||||
|
||||
All you need to do is to pass something like:
|
||||
```
|
||||
--set-string extraEnv[0].name=EXPERIMENTAL_OCI_STORAGE \
|
||||
--set-string extraEnv[0].value=true \
|
||||
```
|
||||
to your helm install or update command.
|
||||
|
||||
Please note you have to use `--set-string` because otherwise the boolean value won't work as expected.
|
||||
|
||||
### Enabling when installing Fleet with Rancher
|
||||
|
||||
You can also activate the experimental features in Fleet when installing Rancher.
|
||||
|
||||
The parameters are the same, but you have to add the `fleet.` prefix.
|
||||
|
||||
```
|
||||
--set-string fleet.extraEnv[0].name=EXPERIMENTAL_OCI_STORAGE \
|
||||
--set-string fleet.extraEnv[0].value=true \
|
||||
```
|
||||
|
|
@ -99,13 +99,5 @@ module.exports = {
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
type: 'category',
|
||||
label: 'Experimental Features',
|
||||
collapsed: false,
|
||||
items:[
|
||||
'enableexperimental'
|
||||
],
|
||||
},
|
||||
],
|
||||
};
|
||||
|
|
|
|||
|
|
@ -4,6 +4,14 @@ Fleet supports experimental features that are disabled by default and that can b
|
|||
|
||||
Enabling/disabling experimental features is done using extra environment variables that are available when deploying `rancher/fleet`.
|
||||
|
||||
See also "[Configure Fleet Install Options in Rancher](./ref-configuration#configure-fleet-install-options-in-rancher)".
|
||||
|
||||
## Available experimental features
|
||||
|
||||
Right now Fleet supports the following experimental features:
|
||||
|
||||
* [`EXPERIMENTAL_OCI_STORAGE`](./oci-storage.md)
|
||||
|
||||
## Enabling an experimental feature
|
||||
|
||||
At the moment we're writing this document, Fleet has OCI storage as an experimental feature.
|
||||
|
|
@ -29,9 +37,3 @@ The parameters are the same, but you have to add the `fleet.` prefix.
|
|||
--set-string fleet.extraEnv[0].name=EXPERIMENTAL_OCI_STORAGE \
|
||||
--set-string fleet.extraEnv[0].value=true \
|
||||
```
|
||||
|
||||
## Available experimental features
|
||||
|
||||
Right now Fleet supports the following experimental features:
|
||||
|
||||
* [`EXPERIMENTAL_OCI_STORAGE`](./oci-storage.md)
|
||||
Loading…
Reference in New Issue