Upgrade strategies accepted by frame2.ENV_UPGRADE_STRATEGY.

This one is special; it is set after a colon and inverts the result.

Do all public first, then all private.

Do all public first, then all private.

On each namespace, only the first Skupper execution will use the old CLI (it is expected to be the init command).

Overwrite the console authentication used Configure with the keywords mode, user and password, separated by commas.

This disruptor will try to change any uses of K8S deployments into DeploymentConfig, on test code: - on actual deployments - on skupper expose As the name says, it will do it 'blindly'; it's useful only for very small and simple tests.

Every skupper site on a private cluster will be created with RouterMode = edge TODO: perhaps move this to a SkupperInstall disruptors file, instead?.

Enables TLS Secret Generation.

Ignore any validator failures, and just keep going no mater what.

Right after setup is complete, update part of the VAN, and then run the tests in this mixed-version network At the end of the test, before the tear down, upgrade the remaining sites and then re-run all tests marked as final The upgrade strategy can be defined on the environment variable SKUPPER_TEST_UPGRADE_STRATEGY.

Any skupper init runs will be overridden to not use the console.

TODO move this to its own file.

This disruptor will cause any services created with http or http2 as their protocol to use tcp instead.

Any namespaces created via f2k8s.CreateNamespaceRaw will receive annotations that force PSA on restricted mode TODO: In the future, make this more configurable (ie, different settings for different levels, or ensure no PSA at all) By default, the version is defined as "latest", but it can be configured with the disruptor configuration "version".

PSADeployment will modify any deployments created by the test code to make them conform the the K8S PSA requirements.

At the end of the test, before the tear down, upgrade all sites and then re-run all tests marked as final This is a very basic upgrade test; it's cheap and simple The upgrade strategy can be defined on the environment variable SKUPPER_TEST_UPGRADE_STRATEGY.