From 977e1e1d8acc8dd9e4653f70b502dcad3426f48f Mon Sep 17 00:00:00 2001 From: vivek thangathurai Date: Tue, 12 Jan 2021 10:37:44 +0530 Subject: [PATCH] make it namespaced install --- .deployments/kubernetes/App.yaml | 2 +- charts/argo/values.yaml | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.deployments/kubernetes/App.yaml b/.deployments/kubernetes/App.yaml index cf372242..bb70abc1 100644 --- a/.deployments/kubernetes/App.yaml +++ b/.deployments/kubernetes/App.yaml @@ -6,7 +6,7 @@ metadata: spec: destination: namespace: argo-helm - server: https://kubernetes.dehklfault.svc + server: https://kubernetes.default.svc project: default source: diff --git a/charts/argo/values.yaml b/charts/argo/values.yaml index cd7d7603..c0f7131c 100644 --- a/charts/argo/values.yaml +++ b/charts/argo/values.yaml @@ -21,16 +21,16 @@ createAggregateRoles: true # Restrict Argo to only deploy into a single namespace by apply Roles and RoleBindings instead of the Cluster equivalents, # and start argo-cli with the --namespaced flag. Use it in clusters with strict access policy. -singleNamespace: false +singleNamespace: true workflow: - namespace: "" # Specify namespace if workflows run in another namespace than argo. This controls where the service account and RBAC resources will be created. + namespace: "argo-ci" # Specify namespace if workflows run in another namespace than argo. This controls where the service account and RBAC resources will be created. serviceAccount: - create: false # Specifies whether a service account should be created + create: true # Specifies whether a service account should be created annotations: {} name: "argo-workflow" # Service account which is used to run workflows rbac: - create: false # adds Role and RoleBinding for the above specified service account to be able to run workflows + create: true # adds Role and RoleBinding for the above specified service account to be able to run workflows controller: image: