Skip to content

Commit 2603b99

Browse files
mbarberofredg02
authored andcommitted
Fixed issue with instances that don't run in $.project.shortName namespace
Eventually, $.kubernetes.agent.namespace should be set to something different from $.kubernetes.master.namespace to run build jobs in separate namespace (see #5), but for now let's stick to same as parent. Signed-off-by: Mikaël Barbero <[email protected]>
1 parent 029af8b commit 2603b99

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

templates/clouds.libsonnet

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
kubernetes(cloudName, config, agents): {
33
[cloudName]: {
44
kind: "kubernetes",
5-
namespace: config.kubernetes.agents.namespace, # should be changed to something agent-specific to fix #5
5+
namespace: config.kubernetes.agents.namespace,
66
podRetention: "never",
77
templates: {
88
[agentName]: agents[agentName].spec + agents[agentName].variants[config.jiroMaster.remoting.version] + {

templates/config.libsonnet

+1-1
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ local clouds = import "clouds.libsonnet";
7070
}
7171
},
7272
agents: {
73-
namespace: $.project.shortName,
73+
namespace: $.kubernetes.master.namespace, # should be changed to something agent-specific to fix #5
7474
defaultResources: {
7575
local Const = import "k8s/resource-packs.libsonnet",
7676
cpu: {

0 commit comments

Comments
 (0)