diff --git a/content/master/concepts/packages.md b/content/master/concepts/packages.md index 48f87886..06a2d276 100644 --- a/content/master/concepts/packages.md +++ b/content/master/concepts/packages.md @@ -285,9 +285,9 @@ In some cases, dependency version downgrade is required for proceeding with installations. Suppose configuration A, which depends on package X with the constraint`>=v0.0.0`, is installed on the control plane. In this case, the package manager installs the latest version of package X, such as `v3.0.0`. Later, you decide -to install configuration Y, which depends on package X with the constraint `<=v2.0.0`. +to install configuration B, which depends on package X with the constraint `<=v2.0.0`. Since version `v2.0.0`satisfies both conditions, package X must be downgraded to -allow the installation of configuration Y which is disabled by default. +allow the installation of configuration B which is disabled by default. For enabling automatic dependency version downgrades, there is a configuration option as a helm value `packageManager.enableAutomaticDependencyDowngrade=true`. @@ -301,7 +301,7 @@ This configuration requires the `--enable-dependency-version-upgrades` flag. Please check the [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section for more details. diff --git a/content/master/concepts/pods.md b/content/master/concepts/pods.md index f6ed4cd0..ce6caa26 100644 --- a/content/master/concepts/pods.md +++ b/content/master/concepts/pods.md @@ -350,7 +350,7 @@ the Helm `values.yml` file or after installation by editing the `Deployment`. The full list of [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section. diff --git a/content/master/concepts/providers.md b/content/master/concepts/providers.md index d64c9cc4..67f89323 100644 --- a/content/master/concepts/providers.md +++ b/content/master/concepts/providers.md @@ -312,9 +312,9 @@ In some cases, dependency version downgrade is required for proceeding with installations. Suppose configuration A, which depends on package X with the constraint`>=v0.0.0`, is installed on the control plane. In this case, the package manager installs the latest version of package X, such as `v3.0.0`. Later, you decide -to install configuration Y, which depends on package X with the constraint `<=v2.0.0`. +to install configuration B, which depends on package X with the constraint `<=v2.0.0`. Since version `v2.0.0`satisfies both conditions, package X must be downgraded to -allow the installation of configuration Y which is disabled by default. +allow the installation of configuration B which is disabled by default. For enabling automatic dependency version downgrades, there is a configuration option as a helm value `packageManager.enableAutomaticDependencyDowngrade=true`. @@ -328,7 +328,7 @@ This configuration requires the `--enable-dependency-version-upgrades` flag. Please check the [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section for more details. diff --git a/content/v1.17/concepts/pods.md b/content/v1.17/concepts/pods.md index f6ed4cd0..ce6caa26 100644 --- a/content/v1.17/concepts/pods.md +++ b/content/v1.17/concepts/pods.md @@ -350,7 +350,7 @@ the Helm `values.yml` file or after installation by editing the `Deployment`. The full list of [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section. diff --git a/content/v1.18/concepts/pods.md b/content/v1.18/concepts/pods.md index f6ed4cd0..ce6caa26 100644 --- a/content/v1.18/concepts/pods.md +++ b/content/v1.18/concepts/pods.md @@ -350,7 +350,7 @@ the Helm `values.yml` file or after installation by editing the `Deployment`. The full list of [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section. diff --git a/content/v1.19/concepts/packages.md b/content/v1.19/concepts/packages.md index 4934456d..3bd1d10f 100644 --- a/content/v1.19/concepts/packages.md +++ b/content/v1.19/concepts/packages.md @@ -285,9 +285,9 @@ In some cases, dependency version downgrade is required for proceeding with installations. Suppose configuration A, which depends on package X with the constraint`>=v0.0.0`, is installed on the control plane. In this case, the package manager installs the latest version of package X, such as `v3.0.0`. Later, you decide -to install configuration Y, which depends on package X with the constraint `<=v2.0.0`. +to install configuration B, which depends on package X with the constraint `<=v2.0.0`. Since version `v2.0.0`satisfies both conditions, package X must be downgraded to -allow the installation of configuration Y which is disabled by default. +allow the installation of configuration B which is disabled by default. For enabling automatic dependency version downgrades, there is a configuration option as a helm value `packageManager.enableAutomaticDependencyDowngrade=true`. @@ -301,7 +301,7 @@ This configuration requires the `--enable-dependency-version-upgrades` flag. Please check the [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section for more details. diff --git a/content/v1.19/concepts/pods.md b/content/v1.19/concepts/pods.md index f6ed4cd0..ce6caa26 100644 --- a/content/v1.19/concepts/pods.md +++ b/content/v1.19/concepts/pods.md @@ -350,7 +350,7 @@ the Helm `values.yml` file or after installation by editing the `Deployment`. The full list of [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section. diff --git a/content/v1.19/concepts/providers.md b/content/v1.19/concepts/providers.md index d64c9cc4..67f89323 100644 --- a/content/v1.19/concepts/providers.md +++ b/content/v1.19/concepts/providers.md @@ -312,9 +312,9 @@ In some cases, dependency version downgrade is required for proceeding with installations. Suppose configuration A, which depends on package X with the constraint`>=v0.0.0`, is installed on the control plane. In this case, the package manager installs the latest version of package X, such as `v3.0.0`. Later, you decide -to install configuration Y, which depends on package X with the constraint `<=v2.0.0`. +to install configuration B, which depends on package X with the constraint `<=v2.0.0`. Since version `v2.0.0`satisfies both conditions, package X must be downgraded to -allow the installation of configuration Y which is disabled by default. +allow the installation of configuration B which is disabled by default. For enabling automatic dependency version downgrades, there is a configuration option as a helm value `packageManager.enableAutomaticDependencyDowngrade=true`. @@ -328,7 +328,7 @@ This configuration requires the `--enable-dependency-version-upgrades` flag. Please check the [configuration options]({{}}) and -[feature flags]({{}}) +[feature flags]({{}}) are available in the [Crossplane Install]({{}}) section for more details.