Unable to deploy fresh Ascender

RobinR1

I'm currently trying to deploy an Ascender deployment in my k3s cluster that also hosts my current AWX deployment. As I'm using SLES, I'm unable to use the installer and since I have ArgoCD installed on the cluster, I created the required kustomization yamls for ArgoCD to deploy the Ascender-operator, similarly as I currently do for my AWX deployment.

The operator (v25.5.1) gets started, the postgresql pod is then started and now it tries to start the ascender-web and -task pods. However in the -task pod, the init-database container fails due to the error:

/bin/sh: line 1: wait-for-migrations: command not found

The image that is used for that container is ghcr.io/ctrliq/ascender-operator:25.5.1 but seems to be missing the wait-for-migrations script ? What could be causing this? Where should this script come from ?

cigamit

wait-for-migrations is definitely on the tasks container.

Logging into my deployed 25.5.1 task container, it is there. Here is where it is added during the build.
ctrliq/ascender-operatorblob/devel/roles/installer/templates/deployments/task.yaml.j2#L118

Can you share a bit of your manifest (randomize anything we shouldn't see) and I can attempt to replicate.

RobinR1

cigamit It turned out that I used the ascender-operator image instead of the ascender image in the ascender.yaml included by the kustomization file causing this. I notices the (waiting) task container and web containers all tried to use the operator image instead of the ascender image. So it was my error, sorry for the confusion.
With this corrected, ascender-task pod seems to go a bit further, but now fails to pull my custom EE image due to
failed to authorize: failed to fetch anonymous token: unexpected status from GET request, despite the ee_pull_credentials_secret being set.

RobinR1

The image that fails to pull is actually the control-pane EE, defined in control_plane_ee_image, so it is not an actual worker EE. Adding

  image_pull_secrets:
    - ascender-ee-pull-credentials
    - ascender-cp-pull-credentials

seems to fix this problem. I should now be able to start playing around with Ascender..