forked from linkerd/linkerd2
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Introduce LINKERD_DOCKER_REGISTRY and flexibilize CI workflows (linke…
…rd#6782) This allows overriding the docker images registry through the `LINKERD_DOCKER_REGISTRY` environment variable, as the CLI's `--registry` flag does (analogously to the `LINKERD_NAMESPACE` env var). In the `integration_tests.yml` workflow we've been wanting to test directly against GH's registry instead of having to endure cr.l5d.io's problems. To achieve this we set `DOCKER_REGISTRY: ghcr.io/linkerd` globally, and all the docker scripts will use it accordingly. And before triggering the integration tests, we copy that value to `LINKERD_DOCKER_REGISTRY`. Note that the CLI and Helm manifests will continue to point to `cr.l5d.io` by default when this is not overridden. `release.yml` still points to `cr.l5.io` because that's what users will experience, so we want to test that right before releasing. Another goal was to be able to run these workflows in forks by overriding the global `DOCKER_REGISTRY` var pointing to the fork's own registry. ## Nice side-effects - This fixes the policy controller's image not being affected by the `--registry` flag when installing through the CLI. - The `--registry` flag (and overriding `LINKERD_DOCKER_REGISTRY` env var) have been added to `linkerd jaeger install`.
- Loading branch information
Showing
16 changed files
with
182 additions
and
75 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
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
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
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
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
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
Oops, something went wrong.