Tommy Li

Hi @kimwnasptd, can you help us update the `kfp-tekton` release to v1.1.1? We patched some fixes for cache deployer to KFP for k8s 1.22 and we have to also update...

This is coming from one of our users who doesn't have much experience as a devops. We probably don't have to disable all the watchers, we only want to disable...

also, this is an opt-out feature, so it shouldn't change the behavior of the current operator deployment.

> Why not just use `kfctl` then? > > Or even better, use the operator-sdk tooling for development - https://github.com/operator-framework/getting-started#2-run-locally-outside-the-cluster For most of our users, kfctl is sufficient in this...

Since the default behavior for operator now is to reapply the kfdef if there a delete event from any kfctl resource, users that made changes to the Kubeflow deployment with...

Thanks @nakfour, pull down the operator pod instance to 0 can be a good option. Then we probably want to add some instructions for: 1. How to stop watching kubeflow...

Thanks @tumido, I can add these instructions to the kubeflow/website and close this issue.

I think this example was created 3 years ago and back then there was no good solution for scalable databases on Kubernetes. But in today's standard, probably is worth to...

/ok-to-test

Thanks @alembiewski, I also published the image to `quay.io/aipipeline/kserve-component:v0.8.0`. Do you want to also include the new tag for this PR?