Upgrading metacontroller to v4.11.22

[tarekabouzeid]

Pull Request Template for Kubeflow Manifests

✏️ Summary of Changes

Upgrading metacontroller to v4.11.22 , issue
Upstream sync PR

📦 Dependencies

List any dependencies or related PRs (e.g., "Depends on #123").

🐛 Related Issues

Link any issues that are resolved or affected by this PR.

✅ Contributor Checklist

• I have tested these changes with kustomize. See Installation Prerequisites.
• All commits are signed-off to satisfy the DCO check.

---

You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

[tarekabouzeid]

cc @juliusvonkohout @varodrig @biswassri

[tarekabouzeid]

Reference here to a similar issue, started since metacontroller V3 , where metacontroller supports only watching CRDs.

A possible solution is changing PPC parent resource to Kubeflow profiles instead of namespaces, and update the hook in upstream to be able to process namespace from Kubeflow profiles CRD .

[juliusvonkohout]

Thank you for the effort. We definitely need to watch namespaces and should not change the order. Because in practice there will be many more profiles created after installing Kubeflow and the metacontroller.

[juliusvonkohout]

canonical/metacontroller-operator#84

Probably means that we have to switch from composite controller to decorator controller. This can be done in the same PR.

[tarekabouzeid]

canonical/metacontroller-operator#84

Probably means that we have to switch from composite controller to decorator controller. This can be done in the same PR.

@juliusvonkohout Thanks for feedback. I found a PR from canonical and done the changes here accordingly.

[juliusvonkohout]

Thank you very much. Can you create the same PR against kubeflow/pipelines, such that we have it synchronized?
Please tag me and @hbelmiro and @HumairAK in that PR. Hopefully we can then merge the PR in kubeflow/pipelines first and then this one afterwards.

Did you also try this locally with some pipelines in a fresh kind cluster?

[tarekabouzeid]

Thank you very much. Can you create the same PR against kubeflow/pipelines, such that we have it synchronized? Please tag me and @hbelmiro and @HumairAK in that PR. Hopefully we can then merge the PR in kubeflow/pipelines first and then this one afterwards.

Did you also try this locally with some pipelines in a fresh kind cluster?

Thank you Julius, I created PR in KFP as well.

I have installed this in a fresh Kind cluster and verified that secret is created. I will try to run some more pipelines locally as well.

[juliusvonkohout]

Please check kubeflow/pipelines#11656 (comment)

[juliusvonkohout]

/lgtm
/approve

[juliusvonkohout]

@tarekabouzeid can you fix the merge conflict?

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: juliusvonkohout

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

The pull request process is described here

Needs approval from an approver in each of these files:

• apps/pipeline/upstream/OWNERS [juliusvonkohout]

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