Skip to content
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

docs: update trg-4-02 #527

Merged
merged 6 commits into from
Jan 11, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/release/trg-4/trg-4-02.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,9 @@
title: TRG 4.02 - Base images
---

:::caution
Proposed release date: "mandatory after": 19th of May 2023
:::

| Status | Created | Post-History |
|--------|-------------|---------------------------------------------------------------------------------|
| Active | 06-Dec-2023 | Add advantages of Dockerhub images
| Draft | 04-May-2023 | Remove notice in favor of dedicated TRG; Add mandatory base image for frontends |
| Active | 25-Nov-2022 | Initial release |

Expand All @@ -23,6 +20,9 @@ As Eclipse Tractus-X project, we don't have automated processes for publishing c
DockerHub is running container scans for all [official images](https://docs.docker.com/trusted-content/official-images/)
and is publishing the scans result in the [docker-library/repo-info repository](https://github.com/docker-library/repo-info).

Utilizing official images from DockerHub is advantageous due to its role as a trusted repository of curated and verified open source containers.
DockerHub provides a centralized platform where developers can access a wide range of pre built containers which adhere to established best practices and meet certain standards of quality, security, and reliability, giving developers confidence in the integrity of the containers they deploy. By incorporating prepared images, teams can foster consistency across environments, reduce the likelihood of vulnerabilities, and accelerate the overall software delivery pipeline rather than managing complex container configurations from scratch.

We are leveraging this information by restricting the base images we use for our published container images to a minimal set.
Aligning on specific base images also gives us the opportunity to provide you with templates for the legal notice,
like described in [TRG 4.06 - Notice for docker images](./trg-4-06.md)
Expand Down
4 changes: 0 additions & 4 deletions docs/release/trg-4/trg-4-05.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,6 @@
title: TRG 4.05 - Container registries
---

:::caution
Proposed release date: "mandatory after": 19th of May 2023
:::

| Status | Created | Post-History |
|--------|--------------|-------------------------------------------------------------------------|
| Draft | 04-May-2023 | Place DockerHub as mandatory container registry; remove GHCR references |
Expand Down
4 changes: 0 additions & 4 deletions docs/release/trg-4/trg-4-06.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,6 @@
title: TRG 4.06 - Notice for docker images
---

:::caution
Proposed release date: "mandatory after": 19th of May 2023
:::

| Status | Created | Post-History |
|--------|-------------|------------------|
| Draft | 04-May-2023 | Initial release |
Expand Down