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

linux_agent_profile.ssh_keys ignores all but the first ssh_key #1940

Closed
lfshr opened this issue Sep 18, 2018 · 3 comments · Fixed by #3099
Closed

linux_agent_profile.ssh_keys ignores all but the first ssh_key #1940

lfshr opened this issue Sep 18, 2018 · 3 comments · Fixed by #3099

Comments

@lfshr
Copy link
Contributor

lfshr commented Sep 18, 2018

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

  • Terraform v0.11.8
  • provider.azurerm v1.15.0

Affected Resource(s)

  • azurerm_kubernetes_cluster

Terraform Configuration Files

resource "azurerm_kubernetes_cluster" "test" {
  name                = "test-cluster"
  resource_group_name = "test-rg"
  location            = "West Europe"
  dns_prefix          = "test"
  kubernetes_version  = "1.10.6"

  linux_profile {
    admin_username = "lfshr"

    ssh_key = {
        key_data = "ssh-rsa ..."
    }

    ssh_key = {
        key_data = "ssh-rsa ..."
    }
  }

  agent_pool_profile {
    name            = "default"
    count           = "3"
    vm_size         = "Standard_DS1_v2"
    os_type         = "Linux"
    os_disk_size_gb = 30
  }

  service_principal {
    client_id     = "..."
    client_secret = "..."
  }
}

Expected Behavior

A cluster should be created with two SSH keys attached to the agents.

Actual Behavior

A cluster is created with only the first ssh_key enabled on the agent, the rest are ignored.

Steps to Reproduce

  1. Create a cluster with 2 ssh_keys using Terraform
  2. Try and connect to agent using the second ssh key

Important Factoids

References

@lfshr
Copy link
Contributor Author

lfshr commented Sep 18, 2018

@katbyte I see you've touched this code in the past. Is there a reason only the first key is used? If so, is it better to add a limit of 1 to the schema?

@ghost
Copy link

ghost commented Apr 3, 2019

This has been released in version 1.24.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
	version = "~> 1.24.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Apr 21, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants