我必须通过Terraform创建一个k8s作业,并以某种方式组织等待该作业完成的机制(因为Terraform无法完成此https://github.com/terraform-providers/terraform-provider-kubernetes/issues/534)。我发现没有什么比使用空资源和一个等待k8s作业的命令(即kubectl wait)更好的了。这些东西将在配置项上的Docker容器中执行。此外,我需要穿过堡垒才能到达k8s集群。为此,我使用SSH隧道:
provider "ssh" {
port = ....
}
provider "kubernetes" {
config_context = "..."
config_context_cluster = "..."
host = "api.${k8s_host}:${data.ssh_tunnel.k8s.port}"
}
data "ssh_tunnel" "k8s" {
host = "bastion.....com"
local_address = "localhost:0"
remote_address = "api.${k8s_host}:443"
}所有k8s资源都已成功创建,因此我假设SSH隧道工作正常。但是如何将它用于空资源呢?这就是它:
resource "null_resource" "wait" {
provisioner "local-exec" {
connection {
type = "ssh"
bastion_host = data.ssh_tunnel.k8s.host
bastion_private_key = file("~/.ssh/id_rsa")
bastion_port = data.ssh_tunnel.k8s.port
host = "api.${k8s_host}"
port = 443
}
command = "kubectl wait ...."
}
triggers = {
job_ids = join(", ", kubernetes_job.a-job.*.id)
}
}但不幸的是,我得到了“到服务器api的连接。${k8s_host}被拒绝-您是否指定了正确的主机或端口?”
因此这里有两个问题: 1.如何以不同的方式等待作业2.如果1不可能(我确信它是不可能的),如何以正确的方式重用SSH隧道。
附言:是的,我读了https://www.terraform.io/docs/provisioners/connection.html文档,但我确实做错了。
发布于 2020-04-16 17:37:13
我想出了如何重用由Terraform打开的SSH隧道:
resource "null_resource" "wait" {
provisioner "local-exec" {
command = "kubectl wait --server=https://api.${k8s_host}:${data.ssh_tunnel.k8s.port} --for=condition=complete --timeout=3000s job/a-job"
}
triggers = {
job_ids = join(", ", kubernetes_job.a-job.*.id)
}
}https://stackoverflow.com/questions/61174233
复制相似问题