09a97bd158
Controller plugins that land on the same node will collide over their CSI `mount_dir`, so give them enough room in our tests that they don't land on the same host. Also, version bump the EBS node plugins to match the controllers.
49 lines
1.1 KiB
HCL
49 lines
1.1 KiB
HCL
# jobspec for running CSI plugin for AWS EBS, derived from
|
|
# the kubernetes manifests found at
|
|
# https://github.com/kubernetes-sigs/aws-ebs-csi-driver/tree/master/deploy/kubernetes
|
|
|
|
job "plugin-aws-ebs-nodes" {
|
|
datacenters = ["dc1", "dc2"]
|
|
|
|
constraint {
|
|
attribute = "${attr.kernel.name}"
|
|
value = "linux"
|
|
}
|
|
|
|
# you can run node plugins as service jobs as well, but this ensures
|
|
# that all nodes in the DC have a copy.
|
|
type = "system"
|
|
|
|
group "nodes" {
|
|
task "plugin" {
|
|
driver = "docker"
|
|
|
|
config {
|
|
image = "amazon/aws-ebs-csi-driver:v0.6.0"
|
|
|
|
args = [
|
|
"node",
|
|
"--endpoint=unix://csi/csi.sock",
|
|
"--logtostderr",
|
|
"--v=5",
|
|
]
|
|
|
|
privileged = true
|
|
}
|
|
|
|
csi_plugin {
|
|
id = "aws-ebs0"
|
|
type = "node"
|
|
mount_dir = "/csi"
|
|
}
|
|
|
|
# note: there's no upstream guidance on resource usage so
|
|
# this is a best guess until we profile it in heavy use
|
|
resources {
|
|
cpu = 500
|
|
memory = 256
|
|
}
|
|
}
|
|
}
|
|
}
|