github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/test/e2e_node/jenkins/image-config.yaml

19 lines
814 B
YAML
Raw Normal View History

node_e2e: configure gce images via config file This file provides the abiliy to specify image project on a per-image basis and is more extensible for future changes. For backwards compatibility and local development convenience, the existing flags are kept and should work.
2016-07-08 21:24:25 +00:00
# To copy an image between projects:
# `gcloud compute --project <to-project> disks create <image name> --image=https://www.googleapis.com/compute/v1/projects/<from-project>/global/images/<image-name>`
# `gcloud compute --project <to-project> images create <image-name> --source-disk=<image-name>`
images:
ubuntu-docker10:
Update ubuntu image to e2e-node-ubuntu-trusty-docker10-v2-image.
2016-11-22 09:00:11 +00:00
image: e2e-node-ubuntu-trusty-docker10-v2-image
node_e2e: configure gce images via config file This file provides the abiliy to specify image project on a per-image basis and is more extensible for future changes. For backwards compatibility and local development convenience, the existing flags are kept and should work.
2016-07-08 21:24:25 +00:00
project: kubernetes-node-e2e-images
node_e2e: Use upstream CoreOS image directly
2016-08-03 19:01:08 +00:00
coreos-alpha:
image: coreos-alpha-1122-0-0-v20160727
project: coreos-cloud
test/node-e2e: Update CoreOS update disabling This disables update-engine and locksmithd with ignition instead of cloud-init so that they're really totally 100% disabled. Pretty much every way of disabling them with cloud-init is mildly racy. Fixes #31633
2016-08-29 23:02:50 +00:00
metadata: "user-data<test/e2e_node/jenkins/coreos-init.json"
node_e2e: configure gce images via config file This file provides the abiliy to specify image project on a per-image basis and is more extensible for future changes. For backwards compatibility and local development convenience, the existing flags are kept and should work.
2016-07-08 21:24:25 +00:00
containervm:
Update the containervm image to the latest one (container-v1-3-v20160604).
2016-09-21 17:24:22 +00:00
image: e2e-node-containervm-v20160604-image
node_e2e: configure gce images via config file This file provides the abiliy to specify image project on a per-image basis and is more extensible for future changes. For backwards compatibility and local development convenience, the existing flags are kept and should work.
2016-07-08 21:24:25 +00:00
project: kubernetes-node-e2e-images
Node e2e can run tests against GCE images based on a regex. It can run tests against multiple existing images that match a regex. GCI images will be using a regex. Signed-off-by: Vishnu kannan <vishnuk@google.com>
2016-07-30 00:55:01 +00:00
gci-family:
Bump GCI version to gci-dev-56-8977-0-0
2016-11-11 23:31:49 +00:00
image_regex: gci-dev-56-8977-0-0
adding gci to node e2e Signed-off-by: Vishnu kannan <vishnuk@google.com>
2016-07-25 21:51:53 +00:00
project: google-containers
adding instance metadata for gci Signed-off-by: Vishnu kannan <vishnuk@google.com>
2016-07-29 20:49:45 +00:00
metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml"