Feature request — gardenctl / direct Gardener API access or native IaC support

[senare]

Summary

Hi Cleura support,

I'm provisioning Gardener shoot clusters on Cleura and want to manage cluster lifecycle through infrastructure-as-code tooling.

The rest.cleura.cloud REST API covers the basics (create, delete, kubeconfig), but the IaC story is limited. A few questions:

1. gardenctl / garden cluster kubeconfig

The Gardener ecosystem has first-class tooling — gardenctl, the Gardener Terraform provider, Crossplane provider — that all require access to the garden cluster kubeconfig. Cleura doesn't expose this. Is there a path to providing garden-level API access, even project-scoped?

2. Terraform provider

Is a Terraform provider for Cleura's Gardener REST API on the roadmap? The OpenStack provider covers the infra layer but doesn't model shoot clusters. Even a minimal provider covering create/delete/kubeconfig would cover most automation use cases.

3. Crossplane

Any plans for a Crossplane provider? The generic provider-http can wrap REST APIs but lacks proper lifecycle semantics — status polling, deletion hooks. A native provider would be significantly cleaner.

Thanks

Documentation category

How-to guide

URL path

No response

My suggestion

The Gardener section documents the web UI and basic shoot cluster concepts but
is missing documentation on programmatic cluster management.

Specifically:

• A complete REST API reference for the Gardener endpoints
  (authentication, bootstrap, shoot create/delete/status, kubeconfig fetch)
• IaC options: does Cleura plan a Terraform provider or Crossplane provider
  for shoot cluster lifecycle?
• Whether gardenctl or direct garden cluster API access is available or planned

Currently the only way to manage clusters programmatically is by
reverse-engineering the REST API from partial examples. A dedicated
"Managing clusters via API" page would cover this.

Additional context

No response

[fghaas]

Hello, I'm afraid there's been a misunderstanding about the purpose of a feature request in the context of this repo. :) Here is where we track documentation feature requests — i.e. coverage for something that Cleura Cloud already does, but that is missing from the docs or could use more detail.

If you already are a Cleura Cloud customer, please refer to Raising Support Issues on how to raise a Feedback issue, where you can put in your feature request. Ideally, please create 3, one for each of your requested features. If you are not (yet) a customer, please refer to the Get Help page on our website. Thank you!

[senare]

I understand the docs repository is only for documentation coverage.

As someone evaluating Cleura's Gardener offering, I'm trying to understand the supported automation model for shoot cluster lifecycle management.

Specifically:

• Is the supported approach to use the REST API directly?
• Is there currently any supported Terraform integration?
• Is gardenctl or garden cluster API access intentionally unavailable?
• Are there examples of customers managing shoot lifecycle from CI/CD pipelines?

I'm not asking for roadmap commitments; I'm trying to understand the recommended automation path.

So, no misstake I am trying out the service (I would expect you to maintain a roadmap). I am only interested in finding out how I am supposed to manage cluster lifecycle from IAC or say any sort of automated pipeline ?

https://backend-engineering-strategy-tools.github.io/site/public-notes/kubernetes/gardener/