Skip to content

Add STACKIT - #3287

Merged
tormath1 merged 1 commit into
flatcar:mainfrom
stackitcloud:stackit
Dec 11, 2025
Merged

tormath1 merged 1 commit into
flatcar:mainfrom
stackitcloud:stackit

Conversation

@robinschneider

Copy link
Copy Markdown
Member

Add new provider STACKIT for testing.

Add CI automation for vendor testing of provider STACKIT.

How to use

Run in CI or locally with all required environment variables.

Testing done

[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]

  • Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
  • Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

@tormath1 tormath1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks, it looks good. We just need to plug the garbage collection as well (you can see here: https://github.com/flatcar/scripts/pull/2873/files how it's done)

Comment thread ci-automation/vendor-testing/stackit.sh
Comment thread ci-automation/vendor-testing/stackit.sh Outdated
Comment thread ci-automation/vendor-testing/stackit.sh Outdated
Comment thread ci-automation/vendor-testing/stackit.sh
Comment thread ci-automation/vendor-testing/stackit.sh Outdated
@github-project-automation github-project-automation Bot moved this from ⚒️ In Progress to ✅ Testing / in Review in Flatcar tactical, release planning, and roadmap Dec 4, 2025
@tormath1

tormath1 commented Dec 4, 2025

Copy link
Copy Markdown
Contributor

So amd64 testing is working fine:

1..31
ok - cl.ignition.v2.noop
ok - cl.internet
ok - docker.network-openbsd-nc
ok - cl.ignition.kargs
ok - cl.basic
ok - coreos.ignition.resource.remote
ok - cl.ignition.misc.empty
ok - coreos.ignition.sethostname
ok - linux.nfs.v3
ok - cl.ignition.v2.btrfsroot
ok - cl.flannel.vxlan
ok - cl.ignition.v1.noop
ok - cl.install.cloudinit
ok - cl.flannel.udp
ok - kubeadm.v1.32.4.cilium.base
ok - kubeadm.v1.33.0.flannel.base
ok - cl.cloudinit.basic
ok - kubeadm.v1.33.0.cilium.base
ok - linux.nfs.v4
ok - kubeadm.v1.33.0.calico.base
ok - coreos.ignition.ssh.key
ok - coreos.ignition.resource.local
ok - coreos.ignition.once
ok - kubeadm.v1.32.4.flannel.base
ok - kubeadm.v1.34.1.cilium.base
ok - cl.network.initramfs.second-boot
ok - cl.etcd-member.discovery
ok - coreos.ignition.security.tls
ok - kubeadm.v1.34.1.flannel.base
ok - kubeadm.v1.32.4.calico.base
ok - kubeadm.v1.34.1.calico.base

If we want to enable ARM64 testing, we need to proceed similar to Hetzner. First we add the two instances types in the following format:

: ${HETZNER_amd64_INSTANCE_TYPE:="cpx11"}
: ${HETZNER_arm64_INSTANCE_TYPE:="cax11"}

Then we set the instance type based on the arch:

hetzner_instance_type_var="HETZNER_${CIA_ARCH}_INSTANCE_TYPE"
hetzner_instance_type="${!hetzner_instance_type_var}"

To finally pass it to Mantle:

--hetzner-server-type="${hetzner_instance_type}" \

Comment thread ci-automation/vendor-testing/stackit.sh
Comment thread ci-automation/ci-config.env Outdated
Signed-off-by: Robin Schneider <[email protected]>

@tormath1 tormath1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Similar to Mantle PR, this has been tested successfully on ARM64 and AMD64.

@tormath1
tormath1 merged commit bc844a9 into flatcar:main Dec 11, 2025
4 checks passed
@github-project-automation github-project-automation Bot moved this from ✅ Testing / in Review to Implemented in Flatcar tactical, release planning, and roadmap Dec 11, 2025
@tormath1

Copy link
Copy Markdown
Contributor

Cherry-picked to:

  • flatcar-4515
  • flatcar-4459

@tormath1 tormath1 mentioned this pull request Dec 11, 2025
6 tasks done
John15321 added a commit to flatcar/Flatcar that referenced this pull request Apr 29, 2026
This PR adds Robin Schneider (@robinschneider) as a Flatcar maintainer.
Adding Robin was proposed on the Maintainers private email list, the
vote was successful (simple majority, no dissentient vote).

The CNCF registries will be updated shortly. 

---

Proposal for reference:

Hello team,

I would like to propose including Robin Schneider[1] as a Flatcar
maintainer. Robin has been a very active participant in the Flatcar
community, regularly helping users, sharing practical feedback, and
contributing to discussions across several areas of the project. He has
also contributed to Flatcar infrastructure and provider enablement work,
and has expressed interest in supporting the infrastructure side of the
project wherever possible. Having him within the maintainer team will
greatly help the project.

Some of Robin's work includes:
- Adding STACKIT as a supported cloud provider for Flatcar by providing
the OEM image integration[2]
- Adding STACKIT provider testing support and CI automation for vendor
testing[3]
- Documenting Flatcar usage on STACKIT for users and operators[4]
- Improving the development workflow by fixing the SDK container startup
on macOS[5]
- Updating the NVIDIA GPU usage documentation, including installation,
container verification, and Kubernetes usage[6]
- Investigating and driving work around getting the NVIDIA GPU Operator
working on Flatcar[7]
- Actively participating in the Flatcar community, helping users, and
bringing practical production-user feedback to the project

Please submit your vote via this email.

[1] https://github.com/robinschneider
[2] flatcar/scripts#3018
[3] flatcar/scripts#3287
[4] flatcar/flatcar-website#456
[5] flatcar/scripts#3814
[6] flatcar/flatcar-website#515
[7] #1962
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants