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

Example cluster_one_nodegroup_with_net_infra does not work properly #40

Closed
gyrter opened this issue Nov 3, 2022 · 7 comments
Closed

Comments

@gyrter
Copy link

gyrter commented Nov 3, 2022

Hello. Your examples are perfect, but i found little problem with cluster_one_nodegroup_with_net_infra

It did not create node group if you specify keypair

╷
│ Error: error creating nodegroup: unable to find new nodegroup by ID after creating
│ 
│   with module.kubernetes_front_nodegroup.selectel_mks_nodegroup_v1.nodegroup_1,
│   on terraform-examples/modules/mks/nodegroup/main.tf line 1, in resource "selectel_mks_nodegroup_v1" "nodegroup_1":
│    1: resource "selectel_mks_nodegroup_v1" "nodegroup_1" {
│ 
╵
╷
│ Error: error creating nodegroup: unable to find new nodegroup by ID after creating
│ 
│   with module.kubernetes_system_nodegroup.selectel_mks_nodegroup_v1.nodegroup_1,
│   on terraform-examples/modules/mks/nodegroup/main.tf line 1, in resource "selectel_mks_nodegroup_v1" "nodegroup_1":
│    1: resource "selectel_mks_nodegroup_v1" "nodegroup_1" {
│ 
╵
╷
│ Error: error creating nodegroup: unable to find new nodegroup by ID after creating
│ 
│   with module.kubernetes_nodegroup.selectel_mks_nodegroup_v1.nodegroup_1,
│   on terraform-examples/modules/mks/nodegroup/main.tf line 1, in resource "selectel_mks_nodegroup_v1" "nodegroup_1":
│    1: resource "selectel_mks_nodegroup_v1" "nodegroup_1" {
│ 
@syedammar111
Copy link

Even if you dont specify keypair, it is giving me the same issue. Did you get a solution to this?

@TawR1024
Copy link

TawR1024 commented Mar 4, 2023

@syedammar111 Hey, which keypair do you use, domain or project ? Can you give an example of your manifest ?

@syedammar111
Copy link

I am not even using a keypair and still receiving this error:
Error: error creating nodegroup: unable to find new nodegroup by ID after creating

@TawR1024
Copy link

TawR1024 commented Mar 7, 2023

Which terraform-provider do you use?
Current stable version is v3.9.1, I have tried to create cluster without keypair and it works properly. Please show your terraform manifest.

my main.tf

...
module "kubernetes_nodegroup" {
  source = "../../../modules/mks/nodegroup"
  cluster_id        = module.kubernetes_cluster.cluster_id
  project_id        = module.kubernetes_cluster.project_id
  region            = module.kubernetes_cluster.region
  availability_zone = var.availability_zone
  nodes_count       = var.nodes_count
  keypair_name      = var.keypair_name
  affinity_policy   = var.affinity_policy
  cpus              = var.cpus
  ram_mb            = var.ram_mb
  volume_gb         = var.volume_gb
  volume_type       = var.volume_type
  labels            = var.labels
  taints            = var.taints 
}

my vars.tf

...
variable "keypair_name" {
  default = ""
}

Also, keypair is optional, so you can skip it.

@gyrter
Copy link
Author

gyrter commented Mar 30, 2023

Also, keypair is optional, so you can skip it.

But I want to connect to nodes over ssh. It can help with some tasks.

@Koodt
Copy link
Collaborator

Koodt commented Jun 5, 2023

> │ Error: error creating nodegroup: unable to find new nodegroup by ID after creating

Hi! Looks like quota was exceeded. Can you send ticket to our support team, please?

@Koodt
Copy link
Collaborator

Koodt commented Jun 5, 2023

Also, keypair is optional, so you can skip it.

But I want to connect to nodes over ssh. It can help with some tasks.

Hi! This option will be deprecated in next MKS API release. Won't fix.

@Koodt Koodt closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2023
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

4 participants