Add Gardener plugin

[mbuechse]

based on d01dc2b (initial working state vibe-coded by @benedikt-haug)

[mbuechse]

The plugin is working now.
This PR does not yet add an entry to the overview table in the compliance monitor. For that, we would also need a recent k8s v1.33, and ideally, a way to automatically enumerate available patch versions, so the latest one could be selected automatically.

[fkr]

Wohoo. this is really cool. Thanks for your work @mbuechse and @benedikt-haug!

[benedikt-haug]

LGTM

[mbuechse]

@benedikt-haug We still need to solve the issue of finding the most recent patch version automatically, and I would need v1.33 (or v1.35) as well. Currently, the patch version is not recent enough (which is the only testcase that does fail):

ERROR: The K8s cluster version 1.34.5 of cluster 'garden-nkhv1db5ym--noris-1-34-external' is outdated according to the standard.

I suppose the reason would be that new patch versions MUST be made available within a month.

[depressiveRobot]

This issue #794 seems to be related. What do you think, can it be closed with this PR?

[depressiveRobot]

If it's still in progress, should we convert it to draft?

[mbuechse]

If it's still in progress, should we convert it to draft?

I think it's a major milestone. We can easily add the rest separately if this gets merged. But we can also keep this open and add the rest here. I don't care. I wouldn't convert it to draft though because it's quite solid, we just need to add a small feature.

[depressiveRobot]

Thank you from me as well for your work @mbuechse and @benedikt-haug :)

As said, there seem to be no blockers here anymore. Let's merge.

[benedikt-haug]

@mbuechse
1.34.6 and 1.33.10 should be recent enough and available:

If you just want the latest and greatest supported version, exempting the k8s version should do the trick.

[mbuechse]

@benedikt-haug I want the latest 1.33 and the latest 1.34. How is the dropdown from the screenshot populated? Can we get this information from some k8s resources via kubectl?

[benedikt-haug]

@benedikt-haug I want the latest 1.33 and the latest 1.34. How is the dropdown from the screenshot populated? Can we get this information from some k8s resources via kubectl?

Those versions are configured in a resource called cloudprofile. Though I'm unsure whether your service account can list them.

Another way I could think off would be to parse the upstream k8s release calendar and trying to deploy the correct version.