Skip to content

docs: rework flavor, cname and related terms after ADR0034 and ADR0035, add links to feature references, dark and light mode images, extend glossary#92

Open
yeoldegrove wants to merge 5 commits into
mainfrom
docs/flavor_cname
Open

docs: rework flavor, cname and related terms after ADR0034 and ADR0035, add links to feature references, dark and light mode images, extend glossary#92
yeoldegrove wants to merge 5 commits into
mainfrom
docs/flavor_cname

Conversation

@yeoldegrove

@yeoldegrove yeoldegrove commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

This is an aggregated PR for:

It includes:

  • docs: rework flavor, cname and related terms after ADR0034 and ADR0035
  • add links to feature references
  • dark and light mode images
  • extend glossary

Which issue(s) this PR fixes:
Fixes gardenlinux/gardenlinux#4600

@netlify

netlify Bot commented Jul 1, 2026

Copy link
Copy Markdown

Deploy Preview for gardenlinux-docs ready!

Name Link
🔨 Latest commit 4e48267
🔍 Latest deploy log https://app.netlify.com/projects/gardenlinux-docs/deploys/6a4e611ef076d800087ed98c
😎 Deploy Preview https://deploy-preview-92--gardenlinux-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@yeoldegrove yeoldegrove self-assigned this Jul 1, 2026
@yeoldegrove yeoldegrove added this to the 2026-07 milestone Jul 1, 2026
@yeoldegrove yeoldegrove force-pushed the docs/flavor_cname branch 5 times, most recently from 60db5e6 to b3cce2b Compare July 2, 2026 15:45
@yeoldegrove yeoldegrove requested review from a team and nkraetzschmar July 7, 2026 06:50
@yeoldegrove yeoldegrove marked this pull request as ready for review July 8, 2026 07:02

@nkraetzschmar nkraetzschmar left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, just minor nit picks

### Versioned Flavor

The hyphenated string used with the `./build` command that specifies the platform, features, and optionally the architecture for a Garden Linux image. Format: `${platform}-${feature1}-${feature2}-${arch}`. Examples: `kvm-python_dev`, `aws-gardener_prod-amd64`.
A **versioned flavor** is the flavor qualified with a version — the string passed to the `./build` script to invoke a build:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might make sense here to mention that the build can be given any subset of this. So it could work with either of cname, flavour, or versioned flavour, picking defaults for any component that's not specified. But not sure if that's maybe too much detail for the glossary 🤔 so probably good to leave it as is here and just mention this somewhere else.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a section about partial arguments and linked naming hierarchy.


### CNAME (Canonical Name)

The **cname** is the minimal, canonically-sorted encoding of the feature set — and only the feature set. Architecture, version, and commit are not part of the cname:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should include that it is the minimal representation. so e.g. aws-gardener is a valid cname, while aws-cloud-gardener is not, since aws includes cloud, thus explicitly listing cloud is not minimal.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a section explaining Minimality.


Automated tests that validate the correct functionality of a Garden Linux image after it's created. Unit tests verify that the image contains expected packages, configurations, and behaviors. See [ADR-0013](./adr/0013-discontinue-packages-musthave-tests.md) for the decision to discontinue certain package must-have tests, and [ADR-0025](./adr/0025-disable-debsums-tests.md) for the decision to disable debsums tests.

### USI (Unified System Image)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should probably also define UKI and link https://uapi-group.org/specifications/specs/unified_kernel_image/ there and then derive the USI definition from there

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a new UKI entry.

Signed-off-by: Eike Waldt <waldt@b1-systems.de>
On-behalf-of: SAP <eike.waldt@sap.com>
Signed-off-by: Eike Waldt <waldt@b1-systems.de>
On-behalf-of: SAP <eike.waldt@sap.com>
Signed-off-by: Eike Waldt <waldt@b1-systems.de>
On-behalf-of: SAP <eike.waldt@sap.com>
Signed-off-by: Eike Waldt <waldt@b1-systems.de>
On-behalf-of: SAP <eike.waldt@sap.com>
Signed-off-by: Eike Waldt <waldt@b1-systems.de>
On-behalf-of: SAP <eike.waldt@sap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] standardize flavor/feature/platform/cname terms

2 participants