en/latest/walk-through/output-parameters/ #9476
giscus[bot]
bot
Replies: 7 comments 22 replies
-
|
I am getting the following error for submitting this workflow, any help would be appreciated |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, it works! |
Beta Was this translation helpful? Give feedback.
-
|
A more secure way to do that is argo submit -n argo --watch https://raw.githubusercontent.com/argoproj/argo-workflows/main/examples/hello-world.yaml --serviceaccount argo |
Beta Was this translation helpful? Give feedback.
-
|
The above is meant to say use the |
Beta Was this translation helpful? Give feedback.
-
|
Never mind, I gave the line from @jatinkumarg more than a passing glance. Setting the argo namespace to the default admin role of the cluster is a persistent solution. Note that |
Beta Was this translation helpful? Give feedback.
-
|
For the minimal RBAC needed for Workflow pods, see https://argo-workflows.readthedocs.io/en/latest/workflow-rbac/ |
Beta Was this translation helpful? Give feedback.
-
|
What if the value of the parameter is an object? How to automatically mapping all the fields in the object? inputs:
parameters:
- name: message
- value: {
name: "Alif",
age: "2"
}How to access it like this? Because originally it will generate error |
Beta Was this translation helpful? Give feedback.
-
|
Haven't tried these, but some options
- value:
name: "Alif"
age: "2"
- value: "{\"name\": \"Alif\", \"age\": \"2\"}"
|
Beta Was this translation helpful? Give feedback.
-
|
2 and 3 would both work |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Is there a simple way to save all parameters in workflow.parameters into a txt file for audit purposes? |
Beta Was this translation helpful? Give feedback.
-
|
They should be saved on the Workflow resource itself. If you use Archived Workflows, then they should be saved in the archive DB. I believe that should suffice for audit purposes. You could write a script to extract just the parameters. |
Beta Was this translation helpful? Give feedback.
-
|
I am getting below error when running workflow using above template |
Beta Was this translation helpful? Give feedback.
-
|
Did u made a service account which has enough permissions? |
Beta Was this translation helpful? Give feedback.
-
|
There is a page in the docs on Workflow RBAC. In this case, both failed and hence the error message, which says what RBAC is needed. The fallback should also be mentioned in the logs just above this message. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for late update. It was permission issue for that service account. I solved that but forgot to mention the update here. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to pass secrets between two steps? For example, step 1 creates an user with password and step 2 sends it to the end user. How would you pass the password between the two steps without exposing it? |
Beta Was this translation helpful? Give feedback.
-
|
The recommended way to use secrets is to use the k8s Secret resource. You could have step 1 create a new k8s Secret and then step 2 mounts that Secret or uses it as an environment variable. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @agilgur5 is this still the recommended path? Or is there some way to secure pass the credentials directly to the next step? |
Beta Was this translation helpful? Give feedback.
-
|
I have an tricky use case with outputs: I am using a argo manifest with a sparkoperator section, and a json in the raw form to submit a simple python script as a task In this Python file I launch, can I access the outputs parameters files ? I mean can I write in the /tmp/response.txt from my prog.py, or is outputs an argo concept ? ======================================================================== - name: spark-main-app-template
inputs:
parameters:
- name: my-user
- name: my-password
- name: my-namespace
- name: my-app-name
artifacts:
- name: sparkapp
path: /tmp/spark-app.json
raw:
data: |
{
"apiVersion": "sparkoperator.k8s.io/v1beta2",
"kind": "SparkApplication",
"metadata": {
"name": "my-main-python",
"namespace": "ns2023"
},
"spec": {
"type": "Python",
"mode": "cluster",
"image": "repo-0.repos.corp.com/my-user/my-img:0.0",
"imagePullSecrets": "docker-secret"
"imagePullPolicy": "Always",
"mainApplicationFile": "local:///opt/spark/workdir/scripts/prog.py",
"sparkVersion": "3.4",
"restartPolicy": {
"type": "Never"
},
"driver": {
"cores": 1,
"coreLimit": "1200m",
"memory": "512m",
"labels": {
"version": "3.4"
},
"env": [
{
"name": "AWS_ACCESS_KEY_ID",
"valueFrom": {
"secretKeyRef": {
"name": "secret-s3",
"key": "aws-access-key-id"
}
}
},
{
"name": "AWS_SECRET_ACCESS_KEY",
"valueFrom": {
"secretKeyRef": {
"name": "secret-s3",
"key": "aws-secret-access-key"
}
}
}
]
},
"executor": {
"cores": 1,
"coreLimit": "1200m",
"instances": 1,
"memory": "512m",
"labels": {
"version": "3.4"
},
"env": [
{
"name": "AWS_ACCESS_KEY_ID",
"valueFrom": {
"secretKeyRef": {
"name": "secret-s3",
"key": "aws-access-key-id"
}
}
},
{
"name": "AWS_SECRET_ACCESS_KEY",
"valueFrom": {
"secretKeyRef": {
"name": "secret-s3",
"key": "aws-secret-access-key"
}
}
}
]
},
"arguments": [
"> /tmp/resp_status_code.txt"
],
"hadoopConf": {
"fs.s3a.endpoint": "s3.endpoint.mycorp.com",
"fs.defaultFS": "s3a://my-bucket"
},
"sparkConf": {
"spark.ui.view.acls": "acl0"
}
}
}
outputs:
parameters:
- name: response-http-status-code
valueFrom:
path: /tmp/response_status_code.txt
container:
image: repo.repos.mycorp.com/submit-spark-app-image:1.1.0
command:
- python3 |
Beta Was this translation helpful? Give feedback.
-
|
You can use Argo variables to access output parameters. Personally, I've just used a resource template to submit |
Beta Was this translation helpful? Give feedback.
-
|
Ok, that's an idea, but how can I use resource template to submit a Python script ? |
Beta Was this translation helpful? Give feedback.
-
|
Your Python script with AWS keys is inside of the Otherwise you'd either use a container template or a script template for a regular script, not a resource template. You can pass keys through Secrets in Argo, same as any other k8s container. |
Beta Was this translation helpful? Give feedback.
-
|
How to retrieve ENV values from container as Output params? |
Beta Was this translation helpful? Give feedback.
-
|
Your container step would have to output them somewhere. Either to a file or stdout for example. Then they can be used as output parameters. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Another linked question to this - Can we not access the path / file from the base image? |
Beta Was this translation helpful? Give feedback.
-
|
I'll take a look and respond there. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for your response, believe you closed that. However, just 1 last question to clarify my doubts spec:
templates:
- name: ha-container
container:
image: homeassistant/home-assistant:latest |
Beta Was this translation helpful? Give feedback.
-
|
Let's continue the conversation there to keep things relevant. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
en/latest/walk-through/output-parameters/
https://argo-workflows.readthedocs.io/en/latest/walk-through/output-parameters/
Beta Was this translation helpful? Give feedback.
All reactions