PSKE - Cluster Provisioning (Terraform) - documentation uses deprecated provider

[mmueller-rs]

Hello,

In the documentation PSKE - Cluster Provisioning (Terraform), the deprecated provider kubectl is used whose latest release is from 24.03.2022.

Therefore an alternative should be evaluated and documented.

Potential alternatives could be:

• kubernetes
  • In my tests, deploying a Shoot-Cluster via kubernetes_manifest with this provider failed, because of missing list permission for CRDs, see https://github.com/hashicorp/terraform-provider-kubernetes/issues/1665
• kustomization
  • The usage of this provider is a bit complicated and requires basic Kustomization-knowledge, but in theory it works. However, I'd prefer the previous provider if possible, though I couldn't get it to run in our PSKE Cluster.

Best regards, Max

[saschascherrer]

Hallo @mmueller-rs,

thank you for taking time and effort to report this. I am sure @Wieneo or @r3m1n0x of the PSKE team will be able to look into this and take appropriate action.

Kind regards Sascha

[YorK8s]

Hello @mmueller-rs,

The kubectl provider was last updated 2 years ago but is not yet deprecated. We still have the documentation for that provider up, because you basically can copy&paste manifests which makes it very easy to use - especially compared to the kubernetes provider, where you have to manually create a resource definition file.

That being said, I have tried to reproduce what you've had happen. When using our PSKE dashboard to download the kubeconfig, you get a temporary admin kubeconfig. With that you can view, delete and create whatever resources you want - including CRDs. So there should be no problem. When I did a test run with the kubernetes provider I had no issues.

Could you maybe provide me with your provider-config and resource-definition files? What exactly were the errors you were getting?