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

Feature Request: Support cluster addons #721

Closed
barlock opened this issue Sep 3, 2019 · 9 comments
Closed

Feature Request: Support cluster addons #721

barlock opened this issue Sep 3, 2019 · 9 comments
Assignees

Comments

@barlock
Copy link

barlock commented Sep 3, 2019

Provide a native mechanism to configure cluster add-ons.

Equivalent of "ibmcloud ks cluster-addons-*"

Terraform Version

0.11.x

Affected Resource(s)

n/a

@barlock
Copy link
Author

barlock commented Sep 4, 2019

Likely depends on bluemix-go support IBM-Cloud/bluemix-go#148

@somaya10
Copy link

somaya10 commented Sep 6, 2019

👍 in need of this feature!

@bstoutenburgh
Copy link

👍 especially with Cluster Autoscaler moving from a helm chart to an addon.

@hkantare
Copy link
Collaborator

@pauljegouic
Copy link

@hkantare , not working on other resource_group !=Default

provider "ibm" {
    region = "eu-de"
    generation = 2
}

data "ibm_container_vpc_cluster" "cluster" {
  name  = "paul-dataplatform-cluster"
  resource_group_id = "40469f682f5a48ee8f5060da1959d111"
}

resource "ibm_container_addons" "addons" {
  cluster = data.ibm_container_vpc_cluster.cluster.name
  addons {
    name    = "cluster-autoscaler"
    version = "1.0.1"
  }
}


output "cluster" {
  value = data.ibm_container_vpc_cluster.cluster
}
➜  tmp2 terraform apply --auto-approve
data.ibm_container_vpc_cluster.cluster: Refreshing state...
ibm_container_addons.addons: Creating...

Error: Request failed with status code: 404, ServerErrorResponse: {"incidentID":"5d93a32861e3b7ab-CDG","code":"G0004","description":"The specified cluster could not be found. If applicable, make sure that you target the correct account and resource group.","type":"General","recoveryCLI":"To list the clusters you have access to, run 'ibmcloud ks cluster ls'. To list the resource groups that you have access to, run 'ibmcloud resource groups'. To target the resource group, run 'ibmcloud target -g \u003cresource_group\u003e'."}

  on main.tf line 12, in resource "ibm_container_addons" "addons":
  12: resource "ibm_container_addons" "addons" {

Please add support for property resource_group_id

@pauljegouic
Copy link

@kavya498 Please fix this feature

@mailtokun
Copy link

@hkantare , not working on other resource_group !=Default

provider "ibm" {
    region = "eu-de"
    generation = 2
}

data "ibm_container_vpc_cluster" "cluster" {
  name  = "paul-dataplatform-cluster"
  resource_group_id = "40469f682f5a48ee8f5060da1959d111"
}

resource "ibm_container_addons" "addons" {
  cluster = data.ibm_container_vpc_cluster.cluster.name
  addons {
    name    = "cluster-autoscaler"
    version = "1.0.1"
  }
}


output "cluster" {
  value = data.ibm_container_vpc_cluster.cluster
}
➜  tmp2 terraform apply --auto-approve
data.ibm_container_vpc_cluster.cluster: Refreshing state...
ibm_container_addons.addons: Creating...

Error: Request failed with status code: 404, ServerErrorResponse: {"incidentID":"5d93a32861e3b7ab-CDG","code":"G0004","description":"The specified cluster could not be found. If applicable, make sure that you target the correct account and resource group.","type":"General","recoveryCLI":"To list the clusters you have access to, run 'ibmcloud ks cluster ls'. To list the resource groups that you have access to, run 'ibmcloud resource groups'. To target the resource group, run 'ibmcloud target -g \u003cresource_group\u003e'."}

  on main.tf line 12, in resource "ibm_container_addons" "addons":
  12: resource "ibm_container_addons" "addons" {

Please add support for property resource_group_id

I got same error. Please support resource_group_id

@mailtokun
Copy link

opened an issue for tracking : #1920

@hkantare
Copy link
Collaborator

hkantare commented Oct 7, 2020

@hkantare hkantare closed this as completed Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants