en/latest/walk-through/hello-world/

[giscus[bot]]

en/latest/walk-through/hello-world/

https://argo-workflows.readthedocs.io/en/latest/walk-through/hello-world/

[worldsayshi]

Unfortunately docker/whalesay seems to be deprecated. I get this error when trying this Workflow:

Failed to pull image "docker/whalesay": [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/docker/whalesay:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/

[agilgur5]

Oh that must be a recent change in Docker; I ran this image yesterday.

It looks like it's indeed quite dated, last publish 9 years ago: https://hub.docker.com/r/docker/whalesay

Looks like there's an issue for this already: docker/whalesay#6

[worldsayshi]

I found an alternative config that (sort of) works:

apiVersion: argoproj.io/v1alpha1
kind: Workflow                  # new type of k8s spec
metadata:
  generateName: hello-world-    # name of the workflow spec
spec:
  entrypoint: argosay          # invoke the whalesay template
  templates:
    - name: argosay              # name of the template
      container:
        container:
        image: argoproj/argosay:v2
        args: [ echo, "hello" ]
        resources: # limit the resources
          limits:
            memory: 32Mi
            cpu: 100m

The created pod completes successfully and prints the message but I get this error on the Workflow:

Error node hello-world-dbrfg: Error (exit code 1): pods "hello-world-dbrfg" is forbidden: User "system:serviceaccount:default:default" cannot patch resource "pods" in API group "" in the namespace "default"

So it looks like this issue: #12733

[agilgur5]

As is mentioned in that issue and various other places, you need to set RBAC for your executor: https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/

If you installed via the quick-start manifests, there is such a Role bound to the default SA.

[worldsayshi]

Yeah, my bad. I didn't realize I should've used the quick start manifests. Currently using the helm chart. Setting up a user with appropriate role seemed to have done the trick.