Commit graph

2 commits

Author SHA1 Message Date
Quentin de Longraye
141d11575b
refactor(e2e): replace GCR image references with official registries (#60424)
### What does this PR do?

Replaces explicit GCR image-pull references in the E2E framework and tests with official registry endpoints:

- Datadog public image defaults and SSI workloads use `registry.datadoghq.com`.
- Istio ambient images use the existing Docker Hub cache via `InternalDockerhubMirror()`, with pull credentials for `istiod`, CNI, `ztunnel`, and generated waypoints.
- Documentation, image-resolution expectations, and standard-Agent repository recognition follow those endpoints.

Existing image version tags, account-level AWS cache configuration, IAM permissions, and Helm chart URLs are unchanged.

### Motivation

Move image consumers away from GCR and reuse the existing Docker Hub cache for Istio, following the investigation in #58215.

### Describe how you validated your changes

- Agent image-resolution unit tests passed through `dda inv test`.
- Compiled the affected environment packages, Istio component, SSI tests, and NPM suite with Bazel's `compilation_outputs` output group.
- Verified that SSI workload tag `d425e7df` has the same digest on GCR and the official Datadog registry; verified availability of Istio `pilot:1.30.8` and the documentation's Agent image tag at their replacement endpoints.
- Rendered the pinned Istio 1.30.8 charts and verified cached images and pull secrets for `istiod`, CNI, and `ztunnel`, plus the registry and credentials inherited by the generated waypoint template.
- Internet-access registry linter, Python syntax check, and `git diff --check` passed.


Co-authored-by: quentin.delongraye <quentin.delongraye@datadoghq.com>
2026-11-16 12:01:04 +00:00
Ofek Lev
47e5a39d12
Move dev docs to a dedicated root directory (#56908)
### What does this PR do?

Moves the maintained Datadog Agent developer documentation from `docs/public/` to `doc/`, together with its site support files. Published page URLs stay the same.

### Motivation

AI coding agents use repository documentation to guide their changes. Moving maintained guidance into `doc/` gives them one directory to consult, with unfinished and deprecated pages kept in `docs/` until they are reviewed for incorporation or removal.

### Describe how you validated your changes

```text
$ dda run docs build
Syncing dependencies
Build started
No issues found
Build finished in 3.80s

$ dda run docs check-links
🔍 6852 Total (in 973ms) 🔗 989 Unique ✅ 6566 OK 🚫 0 Errors 👻 200 Excluded ⛔ 86 Unsupported


$ dda inv linter.docs-links
Synchronizing dependencies
The documentation references this repository properly

$ dda inv invoke-unit-tests.run --tests=docs_repo_links,docs_links
Synchronizing dependencies
................................
----------------------------------------------------------------------
Ran 32 tests in 0.087s

OK
...
----------------------------------------------------------------------
Ran 3 tests in 0.024s

OK
Running tests from module docs_repo_links_tests

Running tests from module docs_links_tests
```

### Additional Notes

`docs/README.md` lists every retained page and its reason. Unpublished pages, deprecated component guidance, and empty placeholders remain temporarily while their content is reviewed for removal or incorporation.

Co-authored-by: ofek.lev <ofek.lev@datadoghq.com>
2026-09-25 15:18:19 +00:00