elegant-carpenter-7681
01/17/2023, 4:10 PMfancy-eve-65019
01/17/2023, 4:17 PMksa-metaflow needs more privileges. If it's a test environment, you can simply grant "cluster admin" privileges:
kubectl create rolebinding metaflow-admin --clusterrole=admin --serviceaccount=default:ksa-metaflowelegant-carpenter-7681
01/17/2023, 4:19 PMfancy-eve-65019
01/17/2023, 4:20 PMfancy-eve-65019
01/17/2023, 4:21 PMcluster install and run my flows in the default namespacefancy-eve-65019
01/17/2023, 4:22 PMargo namespacemammoth-rainbow-82717
01/17/2023, 4:23 PMmammoth-rainbow-82717
01/17/2023, 4:24 PMmammoth-rainbow-82717
01/17/2023, 4:28 PMapiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
kind: ClusterRole
metadata:
name: workflow-user-role
rules:
- apiGroups:
- ""
resources:
- pods
verbs:
- get
- watch
- apiGroups:
- ""
resources:
- pods/log
verbs:
- get
- watch
- apiGroups:
- <http://argoproj.io|argoproj.io>
resources:
- workflows
verbs:
- get
- create
- apiGroups:
- <http://argoproj.io|argoproj.io>
resources:
- workflowtaskresults
verbs:
- createmammoth-rainbow-82717
01/17/2023, 4:28 PMmammoth-rainbow-82717
01/17/2023, 4:29 PMelegant-carpenter-7681
01/17/2023, 4:30 PMfancy-eve-65019
01/17/2023, 4:32 PMelegant-carpenter-7681
01/17/2023, 4:33 PMSTEP 3.1:
<https://argoproj.github.io/argo-workflows/quick-start/#install-argo-workflows>
$ kubectl apply -n argo -f <https://github.com/argoproj/argo-workflows/releases/download/v3.3.10/install.yaml>
$ kubectl patch deployment \
argo-server \
--namespace argo \
--type='json' \
-p='[{"op": "replace", "path": "/spec/template/spec/containers/0/args", "value": [
"server",
"--auth-mode=server"
]}]'mammoth-rainbow-82717
01/17/2023, 4:37 PMmammoth-rainbow-82717
01/17/2023, 4:37 PMmammoth-rainbow-82717
01/17/2023, 4:38 PMmammoth-rainbow-82717
01/17/2023, 4:39 PMelegant-carpenter-7681
01/17/2023, 10:19 PM