{"action":"closed","issue":{"url":"https://api.github.com/repos/IBM-Cloud/terraform-provider-ibm/issues/188","repository_url":"https://api.github.com/repos/IBM-Cloud/terraform-provider-ibm","labels_url":"https://api.github.com/repos/IBM-Cloud/terraform-provider-ibm/issues/188/labels{/name}","comments_url":"https://api.github.com/repos/IBM-Cloud/terraform-provider-ibm/issues/188/comments","events_url":"https://api.github.com/repos/IBM-Cloud/terraform-provider-ibm/issues/188/events","html_url":"https://github.com/IBM-Cloud/terraform-provider-ibm/issues/188","id":312829699,"number":188,"title":"ibm_container_cluster can not span vlans","user":{"login":"msvechla","id":8947879,"avatar_url":"https://avatars3.githubusercontent.com/u/8947879?v=4","gravatar_id":"","url":"https://api.github.com/users/msvechla","html_url":"https://github.com/msvechla","followers_url":"https://api.github.com/users/msvechla/followers","following_url":"https://api.github.com/users/msvechla/following{/other_user}","gists_url":"https://api.github.com/users/msvechla/gists{/gist_id}","starred_url":"https://api.github.com/users/msvechla/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msvechla/subscriptions","organizations_url":"https://api.github.com/users/msvechla/orgs","repos_url":"https://api.github.com/users/msvechla/repos","events_url":"https://api.github.com/users/msvechla/events{/privacy}","received_events_url":"https://api.github.com/users/msvechla/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-04-10T08:53:11Z","updated_at":"2018-04-10T09:31:00Z","closed_at":"2018-04-10T09:31:00Z","author_association":"NONE","body":"Hello,\r\n\r\nwhen provisioning a cluster, I can only specify workers in a single vlan / subnet.\r\nOnce I add more workers in other vlans via the UI, they successfully join the cluster and show up in the dashboard, however I can not ping or access pods scheduled on them in any way.\r\n\r\nAlso kubectl logs / kubectl exec does not work on pods spawning on the new worker nodes, which reside in vlans other than specified during launch in terraform.\r\n\r\nThis hints, that there is some misconfiguration when launching the cluster, as networking does not work with nodes added later from other vlans.\r\n\r\n### Terraform Version\r\nTerraform v0.11.3\r\n\r\n### Affected Resource(s)\r\nPlease list the resources as a list, for example:\r\n- ibm_container_cluster\r\n\r\n### Terraform Configuration Files\r\n```hcl\r\nresource \"ibm_container_cluster\" \"my-dev-k8s\" {\r\n  name         = \"my-dev-k8s\"\r\n  datacenter   = \"fra02\"\r\n  org_guid     = \"${data.ibm_org.org.id}\"\r\n  space_guid   = \"${data.ibm_space.space.id}\"\r\n  account_guid = \"${data.ibm_account.account.id}\"\r\n  no_subnet    = false\r\n\r\n  kube_version = \"1.9.3\" //TODO: PLEASE ALWAYS CHECK FOR LATEST\r\n\r\n  // One worker will be launched with terraform, all others will be launched via UI\r\n  // This is because we can not choose different subnets / pods during launch\r\n  // Make sure to launch other workers in other pods via the UI\r\n\r\n  workers = [\r\n    {\r\n      name   = \"tf_default_worker\"\r\n      action = \"add\"\r\n    },\r\n  ]\r\n  machine_type    = \"b2c.4x16\"\r\n  isolation       = \"private\"\r\n  public_vlan_id  = \"${data.ibm_network_vlan.public_fra02_pod1.id}\"\r\n  private_vlan_id = \"${data.ibm_network_vlan.private_fra02_pod1.id}\"\r\n}\r\n```\r\n\r\n### Expected Behavior\r\npods scheduled on workers, which have been added via the UI in another subnet than specified in TF should be accessible\r\n\r\n### Actual Behavior\r\npods scheduled on workers, which have been added via the UI in another subnet than specified in TF are not accessible\r\n\r\n### Steps to Reproduce\r\nPlease list the steps required to reproduce the issue, for example:\r\n1. launch a cluster in terraform\r\n2. add another worker via the UI in another vlan than the one specfied in TF\r\n3. try to rub kubectl logs <ID OF POD SCHEDULED ON NEW WORKER IN OTHER VLAN>\r\n\r\n"}}
{"actor":{"display_login":"msvechla"}}