-
Notifications
You must be signed in to change notification settings - Fork 569
allows for image repos to be set via Environment Variables #2705
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -74,8 +74,11 @@ | |
{{$EXEC_TIMEOUT := DefaultParam .CL2_EXEC_TIMEOUT "3600s"}} | ||
{{$SLEEP_AFTER_EXEC_DURATION := DefaultParam .CL2_SLEEP_AFTER_EXEC_DURATION "0s"}} | ||
|
||
{{$registry := DefaultParam .CL2_LATENCY_POD_REGISTRY "registry.k8s.io"}} | ||
{{$latencyPodImage := DefaultParam .CL2_LATENCY_POD_IMAGE (Concat $registry "/pause:3.9")}} | ||
## Image Repositories | ||
{{$registryK8sRepo := DefaultParam .CL2_REGISTRY_K8S_REPO "registry.k8s.io"}} | ||
{{$gcrRepo := DefaultParam .CL2_GCR_REPO "gcr.io"}} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This field and above seem different registries for different images, I'll defer to this repository's maintainers here, but maybe we should try to find some naming that clarifies a bit more where they're set? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same, I'll take any suggestion made from the code owners. |
||
|
||
{{$latencyPodImage := DefaultParam .CL2_LATENCY_POD_IMAGE "pause:3.9"}} | ||
{{$defaultQps := DefaultParam .CL2_DEFAULT_QPS (IfThenElse (le .Nodes 500) 10 100)}} | ||
|
||
{{$ADDITIONAL_MEASUREMENT_MODULES := DefaultParam .CL2_ADDITIONAL_MEASUREMENT_MODULES nil}} | ||
|
@@ -211,6 +214,8 @@ steps: | |
mediumJobsPerNamespace: 1 | ||
smallJobSize: {{$SMALL_GROUP_SIZE}} | ||
smallJobsPerNamespace: 1 | ||
registryK8sRepo: {{$registryK8sRepo}} | ||
gcrRepo: {{$gcrRepo}} | ||
|
||
{{if $ADDITIONAL_PHASES_MODULES}} | ||
{{range $ADDITIONAL_PHASES_MODULES}} | ||
|
@@ -232,6 +237,7 @@ steps: | |
schedulerThroughputNamespaces: {{$schedulerThroughputNamespaces}} | ||
schedulerThroughputPodsPerDeployment: {{$schedulerThroughputPodsPerDeployment}} | ||
deploymentImage: {{$latencyPodImage}} | ||
registryK8sRepo: {{$registryK8sRepo}} | ||
{{end}} | ||
|
||
- module: | ||
|
@@ -356,6 +362,8 @@ steps: | |
mediumJobsPerNamespace: 1 | ||
smallJobSize: {{$SMALL_GROUP_SIZE}} | ||
smallJobsPerNamespace: 1 | ||
registryK8sRepo: {{$registryK8sRepo}} | ||
gcrRepo: {{$gcrRepo}} | ||
|
||
{{if $ADDITIONAL_PHASES_MODULES}} | ||
{{range $ADDITIONAL_PHASES_MODULES}} | ||
|
@@ -402,6 +410,8 @@ steps: | |
smallJobsPerNamespace: 0 | ||
pvSmallStatefulSetSize: {{$SMALL_STATEFUL_SETS_PER_NAMESPACE}} | ||
pvMediumStatefulSetSize: {{$MEDIUM_STATEFUL_SETS_PER_NAMESPACE}} | ||
registryK8sRepo: {{$registryK8sRepo}} | ||
gcrRepo: {{$gcrRepo}} | ||
|
||
{{if $ADDITIONAL_PHASES_MODULES}} | ||
{{range $ADDITIONAL_PHASES_MODULES}} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave this a more descriptive name,
registryK8sRepo
, since there are 2 image registries used and I thought it would help highlight which repo exactly was being specified.