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

Make this repo manageable #107

Open
mxmxchere opened this issue Jun 13, 2024 · 1 comment
Open

Make this repo manageable #107

mxmxchere opened this issue Jun 13, 2024 · 1 comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling epic Issues that are spread across multiple sprints

Comments

@mxmxchere
Copy link
Contributor

mxmxchere commented Jun 13, 2024

We already noticed that there is an issue with the structure of this repo in:

What those have in common and what @paulphys @chess-knight and @mxmxchere have identified as a key-issue is an "artificial" dependency between the cluster-class and the kubernetes version.

Clusterclass is meant to be a template for Cluster-API and cluster-api-provider-openstack resources supporting multiple kubernetes versions. The kubernetes version therefore resides in the cluster-resource and not in the cluster-class.

We should stop putting the kubernetes version inside the ClusterClass name. If we do that, we have the problem that the cso will no longer work.

How many cluster-classes?
One per provider, version stays the same, version is increased on demand not with each k8s version.

Clusterclasses (very few, changed rarely):

  • cluster-class-openstack-v1 (immutable, no renovate (of course)
  • cluster-class-openstack-v2
  • cluster-class-metal3-v1

Cluster-Addons (one per release+k8s combination):

  • cluster-addon-openstack-v1.27
  • cluster-addon-openstack-v1.28
  • cluster-addon-openstack-v1.29

-> Change CSO-behaviour to read only clusterstackname from cluster.spec.topology.class and to read k8s version from cluster.spec.topology.version

Wishlist for the endresult:

  • documentation page (One Page version, parsed out of each cluster-class?)
  • tested clusterstacks (latest cluster-class version with 4 latest addons (k8s-version))
  • renovate/dependabot updating stack-components
@paulphys paulphys changed the title Make this repo managable Make this repo manageable Jun 13, 2024
@paulphys paulphys added Container Issues or pull requests relevant for Team 2: Container Infra and Tooling epic Issues that are spread across multiple sprints labels Jun 13, 2024
@mxmxchere
Copy link
Contributor Author

mxmxchere commented Jun 13, 2024

The folder structure would then look, for example, look like this:

.
├── kubevirt
├── metal3
│   ├── addons
│   │   ├── 1-18
│   │   ├── 1-19
│   │   ├── 1-20
│   │   ├── 1-21
│   │   ├── 1-22
│   │   ├── 1-23
│   │   ├── 1-24
│   │   ├── 1-25
│   │   ├── 1-26
│   │   ├── 1-27
│   │   ├── 1-28
│   │   ├── 1-29
│   │   ├── 1-30
│   │   ├── 1-31
│   │   └── 1-32
│   └── class
│       ├── v1
│       └── v2
└── openstack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling epic Issues that are spread across multiple sprints
Projects
Status: Backlog
Development

No branches or pull requests

2 participants