bump AppWrapper to 1.0.0

[dgrove-oss]

• Update to Kueue 0.10
• Remove deprecated kube-rbac-proxy
• Refactor workload controller to prepare to upstream to Kueue

Combines go.mod changes of #651 with the Makefile change to pick up the CRD.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign christianzaccaria for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ChristianZaccaria]

Perhaps the Makefile can also be updated to use Kueue v0.10.0

[ChristianZaccaria]

I'm getting this error on attempt to create AppWrapper, in the CFO logs:

2025-01-16T20:51:21Z ERROR Unhandled Error {"logger": "UnhandledError", "error": "pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:243: Failed to watch *v1.Namespace: failed to list *v1.Namespace: namespaces is forbidden: User "system:serviceaccount:redhat-ods-applications:codeflare-operator-controller-manager" cannot list resource "namespaces" in API group "" at the cluster scope"}

[dgrove-oss]

I rebased to pick up refreshed go.mod from #655. Building the binary locally is fine.

We'll need to update the go-toolset image in the Dockerfile to something that supports go 1.23 before this can be merged. Otherwise I think it should be ready to go.

[dgrove-oss]

Should be good to go when you are ready to merge.

[ChristianZaccaria]

/lgtm
Thanks!!

Kueue upgrade has been made. We will sync changes to RHOAI as soon as this PR is merged and we sync to downstream as well.

[Ygnas]

/lgtm
I have tested integration with Kueue v0.10.1 and this version of the CFO.

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.