Skip to content

Add Batch landscape files, logos, and CI workflow#2110

Open
stackedsax wants to merge 2 commits intocncf:mainfrom
stackedsax:batch-landscape-files
Open

Add Batch landscape files, logos, and CI workflow#2110
stackedsax wants to merge 2 commits intocncf:mainfrom
stackedsax:batch-landscape-files

Conversation

@stackedsax
Copy link
Copy Markdown

Summary

Migrates the CNCF Batch Subproject landscape from naskio/bsi-landscape into the TOC repo under tags/tag-workloads-foundation/subprojects/batch/landscape/.

  • Adds landscape.yml, settings.yml, netlify.toml, and Brewfile.netlify from the existing landscape repo
  • Adds all 14 project logos (SVGs) to hosted_logos/
  • Adds OpenGRIS as a new K8s-Connectors entry
  • Adds .github/workflows/batch-landscape.yml — scoped CI that only runs on changes to the landscape directory
  • Updates settings.yml to point GitHub links at cncf/toc instead of naskio/bsi-landscape

Netlify

The published landscape at https://bsi-landscape.netlify.app will need to be reconnected to this repo. Once the site is transferred to a CNCF-managed Netlify account, the base directory should be set to:

tags/tag-workloads-foundation/subprojects/batch/landscape

The netlify.toml in that directory handles the rest.

Test plan

  • CI workflow (batch-landscape.yml) validates and builds successfully
  • Netlify site reconnected and publishes from this repo
  • https://bsi-landscape.netlify.app renders correctly after reconnection

Migrates landscape data, logos, and build configuration from
naskio/bsi-landscape into the toc repo under
tags/tag-workloads-foundation/subprojects/batch/landscape/.

Adds a scoped GitHub Actions workflow that only runs on changes
to the landscape directory. Netlify site will need to be
reconfigured to use this repo with base directory set to
tags/tag-workloads-foundation/subprojects/batch/landscape/.

Signed-off-by: stackedsax <alex.scammon@gresearch.co.uk>
Signed-off-by: stackedsax <alex.scammon@gresearch.co.uk>
@stackedsax stackedsax requested review from a team as code owners April 7, 2026 02:38
@stackedsax
Copy link
Copy Markdown
Author

For a little more context, we have this landscape:

But we never had a place to keep the files so they were in a personal repo.  I'd love to consolidate into a more official place now that we have the batch subproject directory available to us.

@github-actions github-actions Bot added needs-triage Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied) needs-kind Indicates an issue or PR that is missing an issue type or kind (a kind/foo label) needs-group Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied) labels Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-group Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied) needs-kind Indicates an issue or PR that is missing an issue type or kind (a kind/foo label) needs-triage Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)

Projects

Status: New
Status: No status
Status: No status
Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant