Matt

I'm not sure I see the use you are looking for. I believe the to_xml shouldn't be changed as that directly converts the defined class into xml based on the...

The v1.1.3 release is still missing from docker hub. Might want to rerelease that so it's get published there.

I moved past that error by moving the hack folder files to a new directory structure `k8s.io/kubernetes/hack/boilerplate` new error says ``` /home/foobar/go/bin/controller-gen "crd:trivialVersions=true,preserveUnknownFields=false" rbac:roleName=manager-role webhook paths="./..." output:crd:artifacts:config=config/crd/bases F0208 15:51:36.863998 4023...

A follow up for auth configuration is do I need to make each `basicAuth` section match in each component. Components being: - server - scheduler - lookout - binoculars -...

This is what I did for my executor(s) config. And that seems to have gotten the queued job to run. ```yaml application: clusterId: aks pool: default executorApiConnection: armadaUrl: apqx-armada-scheduler.rxample.comt:443 basicAuth:...

`025-05-29T19:54:36.904Z WARN queue_cache.go:54 Error fetching queues: rpc error: code = Unauthenticated desc = Invalid credentials presented for user "armada-svc" via auth service "Basic"` getting this error when trying to add...

Another auth issue I noticed seems to be binoculars specific. @dejanzele I am trying to secure this connectivity, but the binoculars configuration doesn't seem to accept anything besides anonymous auth. ...

I did get the groups working... I haven't tried OIDC via the server yet, but I would like to limit user's abilities in the lookout UI. ``` auth: anonymousAuth: false...

When trying to cancel a job in Armada with OIDC from lookout I got. ```json { "error": "Invalid credentials presented via auth service \"OIDC\": oidc: expected audience \"xxxx-armada\" got [\"account\"]",...

I got it working in the Lookout UI, but that’s it. Regards, Matthew Landowski On Fri, Sep 19, 2025 at 17:33 Dmitry Mishin ***@***.***> wrote: > *dimm0* left a comment...