-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[BARX-1713] Auto-detect cloud provider for admission controller container registry #47924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
AliDatadog
wants to merge
6
commits into
main
Choose a base branch
from
ali.benabdallah/admission-controller-auto-registry
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+483
−17
Draft
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0f1ae7c
Auto-detect cloud provider for admission controller container registry
AliDatadog ee9eba7
Use IsConfigured for registry detection, add release notes and E2E tests
AliDatadog d773656
Update release notes: remove egress mention, add docs link
AliDatadog c7f393c
Wire admission-controller E2E tests into GitLab CI
AliDatadog 9698b8b
Run admission controller E2E tests on Kind, EKS, and GKE
AliDatadog cc04ef1
Tighten E2E registry assertions: check exact registry per cloud provider
AliDatadog File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
13 changes: 13 additions & 0 deletions
13
releasenotes-dca/notes/admission-controller-auto-registry-detection-3e96f82298a87d08.yaml
This file contains hidden or 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,13 @@ | ||
| --- | ||
| enhancements: | ||
| - | | ||
| The admission controller now auto-selects the container registry based on the | ||
| detected cloud provider (EKS uses ``public.ecr.aws/datadog``, GKE uses | ||
| ``gcr.io/datadoghq``, AKS uses ``datadoghq.azurecr.io``). The new default for | ||
| environments where no cloud provider is detected is ``registry.datadoghq.com`` | ||
| (previously ``gcr.io/datadoghq``). Explicit configuration via | ||
| ``admission_controller.container_registry`` or webhook-specific overrides still | ||
| takes precedence. To restore the previous default, set | ||
| ``admission_controller.container_registry`` to ``gcr.io/datadoghq``. See | ||
| `Changing your container registry <https://docs.datadoghq.com/containers/guide/changing_container_registry/>`_ | ||
| for all available registries and configuration options. |
11 changes: 11 additions & 0 deletions
11
releasenotes/notes/admission-controller-auto-registry-detection-3e96f82298a87d08.yaml
This file contains hidden or 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,11 @@ | ||
| --- | ||
| enhancements: | ||
| - | | ||
| The default container registry for the admission controller has changed from | ||
| ``gcr.io/datadoghq`` to ``registry.datadoghq.com``. On managed Kubernetes | ||
| environments, the cluster agent now auto-selects a cloud-provider-specific | ||
| registry (EKS: ``public.ecr.aws/datadog``, GKE: ``gcr.io/datadoghq``, AKS: | ||
| ``datadoghq.azurecr.io``). To restore the previous default, set | ||
| ``admission_controller.container_registry`` to ``gcr.io/datadoghq``. See | ||
| `Changing your container registry <https://docs.datadoghq.com/containers/guide/changing_container_registry/>`_ | ||
| for all available registries and configuration options. |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.