mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
As of April 1, Docker Hub rate limits tightened. With only 10 pulls/hr/IP, we're likely to encounter test failures. Switch all Docker images getting pulled from this repository to use the HashiCorp managed registry mirror. Note that most of our tests in `drivers/docker` don't pull from the remote registry but load a local image, while others will need to pull from the remote and fetch different images depending on OS/arch. Refactor the definition of test task configuration to make it clear which is which, and de-factor some false sharing of setup functions. Updates the E2E tests to use that registry by configuring the Docker daemon. This required changing out a few container images that we don't have in the registry, but these new images are all smaller. There are a couple of tests that still use explicitly-tagged `docker.io` images or other third-party registries, which have been left in place. Ref: https://hashicorp.atlassian.net/browse/NET-12233 update E2E images to those in the registry mirror fix windows and docklog test build fix stopsignal test mop-up more mop-up
54 lines
1.3 KiB
HCL
54 lines
1.3 KiB
HCL
# Copyright (c) HashiCorp, Inc.
|
|
# SPDX-License-Identifier: BUSL-1.1
|
|
|
|
# jobspec for running CSI plugin for AWS EFS, derived from
|
|
# the kubernetes manifests found at
|
|
# https://github.com/kubernetes-sigs/aws-efs-csi-driver/tree/master/deploy/kubernetes
|
|
|
|
job "plugin-aws-efs-nodes" {
|
|
datacenters = ["dc1"]
|
|
|
|
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 = "public.ecr.aws/efs-csi-driver/amazon/aws-efs-csi-driver:v1.3.6"
|
|
args = [
|
|
"node",
|
|
"--endpoint=${CSI_ENDPOINT}",
|
|
"--logtostderr",
|
|
"--v=5",
|
|
]
|
|
|
|
privileged = true
|
|
}
|
|
|
|
# note: the EFS driver doesn't seem to respect the --endpoint
|
|
# flag or CSI_ENDPOINT env var and always sets up the listener
|
|
# at '/tmp/csi.sock'
|
|
csi_plugin {
|
|
id = "aws-efs0"
|
|
type = "node"
|
|
mount_dir = "/tmp"
|
|
}
|
|
|
|
# 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
|
|
}
|
|
}
|
|
}
|
|
}
|