Skip to content

chore: Reintroduce subdirs#270

Open
jschoone wants to merge 1 commit into
mainfrom
feat/subdirs
Open

chore: Reintroduce subdirs#270
jschoone wants to merge 1 commit into
mainfrom
feat/subdirs

Conversation

@jschoone

Copy link
Copy Markdown
Contributor

In the Container Call discussed it might be a good idea to bring the subdirs back for two main reasons:

  • CSO does not allow changing the Cluster Stack
  • We can handle breaking changes/new features in new minor versions

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • squash commits
  • include documentation
  • add unit tests

In the Container Call discussed it might be a good idea to bring the
subdirs back for two main reasons:

- CSO does not allow changing the Cluster Stack
- We can handle breaking changes/new features in new minor versions

Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>
@jschoone jschoone requested a review from garloff June 19, 2026 15:12

@garloff garloff left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's avoid too much duplication, so I suggest we

  • try to only have one README (unless we expect significant divergence between them)
  • clean out the references to other minor versions from the subdirectories

I'll push some changes ...

# url: https://nbg1.your-objectstorage.com/osism/openstack-k8s-capi-images/ubuntu-2404-kube-v1.33/ubuntu-2404-kube-v1.33.12.qcow2
# checksum: "sha256:"
# build_date: 2026-05-13
- version: 'v1.34.0'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we need the 1.34.x k8s node images in the 1-33 subdirectory?

@@ -0,0 +1,149 @@
# Cluster Stacks

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we expect changes significant enough between the k8s minor versions that we want to du^Wtriplicate this README file?

- kubernetes: 1.33.11
cinder_csi: 2.33.1
occm: 2.33.1
- kubernetes: 1.34.8

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

As we have a 1-33 subdirectory now, do we want to track any other k8s versions in here?

tags:
- clusterstacks
versions:
- version: 'v1.33.4'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Same comment as before: We don't need 1.33 in the 1-34 directory, do we?

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.

2 participants