-
Notifications
You must be signed in to change notification settings - Fork 150
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
15 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Feature flags | ||
|
||
Some Lagoon features can be controlled by setting feature flags. | ||
This is designed to assist administrators to roll out new features in a controlled manner. | ||
|
||
## Environment variables | ||
|
||
The following environment variables can be set on an environment or project to toggle feature flags. | ||
|
||
| Environment Variable Name | Active scope\* | Version introduced | Version removed | Default Value | Description | | ||
| --- | --- | --- | --- | --- | --- | | ||
| `LAGOON_FEATURE_FLAG_ROOTLESS_WORKLOAD` | `build` | 2.0.0 | - | `enabled` | Set to `disabled` to allow the workload to run as root. This flag will eventually be deprecated, at which point rootless workloads will be enforced. | | ||
| `LAGOON_FEATURE_FLAG_STANDARD_NETWORK_POLICY` | `build` | 2.0.0 | - | `enabled` | Set to `disabled` to stop Lagoon adding a default namespace isolation network policy on deployment. This flag will eventually be deprecated, at which point the default network policy will be enforced.<br>NOTE: disabling this feature will _not_ remove any existing network policy from previous deployments. Those must be removed manually. | | ||
|
||
\* Active scope indicates whether the variable must be set as `build` or `runtime` scope to take effect. `global` sets the variable in both scopes, so that should work too. |