🌈 Feature: Add support for Flatcar Container Linux

[t-lo]

What type of PR is this?

/kind bug
/kind feature

What this PR does / why we need it:

This change adds support for Flatcar to the blobfuse installer. Changes are minimal; we're re-using the rhcos installer script and the gardenlinux paths.

Changes are minimal; we're re-using the rhcos installer script and the gardenlinux paths.

As Flatcar currently does not ship libfuse, we install it alongside blobfuse2, similar to what #2208 does for RHCOS.

Lastly, this change contains a fix for updating PATH in the blobfuse-proxy.service systemd service unit. Previously, the way PATH was modified led to the variable contents being overwritten instead of added to. See 0f30780 for details.

Special notes for your reviewer:

This change was verified by a test cluster deployment by @invidian . Pre-built container images for testing are available from https://github.com/flatcar-hub/blob-csi-driver/pkgs/container/blob-csi .

Release note:

* Installer: Added support for Flatcar Container Linux

[k8s-ci-robot]

Welcome @t-lo!

It looks like this is your first PR to kubernetes-sigs/blob-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/blob-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @t-lo. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[andyzhangx]

/ok-to-test

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, t-lo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andyzhangx]

@t-lo could you also cherrypick this PR to release-1.33? thx

[t-lo]

@andyzhangx I'd be happy to help! Could you please elaborate on release-1.33 ? I see release- branches for 1.23 to 1.27 but no 1.33?

[t-lo]

@andyzhangx I was browsing closed PRs and saw that everything gets backported to 1.26 and 1.27, so I did the same:

• [release 1.27] 🌈 Feature: Add support for Flatcar Container Linux #2213
• [release 1.26] 🌈 Feature: Add support for Flatcar Container Linux #2214

Is this what you're looking for?