[CONTINT-3761] Use GBI for the internal eds-check image #175
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.
What does this PR do?
Migrate the internal
extendeddaemonset-check
image to GBI.Motivation
Security folks want all containers running on our internal infra to be based on a GBI golden base image.
Additional Notes
See DataDog/images#5091.
The idea is to use GBI for the internal image only and to keep UBI as today for the public one.
As the binary is a standalone statically-linked file, it shouldn’t make any difference.
Describe your test plan
Update the version of
extendeddaemonset-check
ink8s-datadog-agent-ops
and check that deployments are still working fine.