Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to delete Kapsule default pool #374

Closed
foux opened this issue Dec 18, 2019 · 2 comments · Fixed by #375
Closed

Unable to delete Kapsule default pool #374

foux opened this issue Dec 18, 2019 · 2 comments · Fixed by #375
Labels
k8s Kubernetes Kapsule issues, bugs and feature requests

Comments

@foux
Copy link

foux commented Dec 18, 2019

Terraform Version

Terraform v0.12.18
+ provider.scaleway v1.13.0

Affected Resource(s)

  • scaleway_k8s_cluster_beta

Terraform Configuration Files

resource "scaleway_k8s_cluster_beta" "cluster" {
    cni           = "cilium"
    name          = "cluster"
    region        = "fr-par"
    tags          = [ "kube"]
    version       = "1.17.0"
}

Debug Output

Error: "default_pool": required field is not set

  on scaleway.tf line 3, in resource "scaleway_k8s_cluster_beta" "cluster":
   3: resource "scaleway_k8s_cluster_beta" "cluster" {

Expected Behavior

We should be able to delete the default pool, if we're using another one

Actual Behavior

We can't delete the default pool, even though we can from the API/web interface

Steps to Reproduce

  1. terraform apply
@debovema
Copy link
Contributor

Hello

I am not sure whether this fix allows to create a scaleway_k8s_cluster_beta resource without any default pool if a scaleway_k8s_pool_beta is created and assigned to the cluster elsewhere.

I tested with master version and it does not work. However I think it should be the expected behaviour, don't you think ?

@Sh4d1
Copy link
Contributor

Sh4d1 commented Feb 7, 2020

Hey @debovema !
You can't create a cluster without a default pool. It's an API limitation. I think it would be kind of hard to mimic such feature on Terraform. So my guess is that it's going to stay like this (and stay coherent with the API).

@remyleone remyleone added the k8s Kubernetes Kapsule issues, bugs and feature requests label Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s Kubernetes Kapsule issues, bugs and feature requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants