fix: the cache server in combination with kubeflow profile quotas

[juliusvonkohout]

Caching is not compatible with profile quotas that specify CPU requests. #5695 is overwritten by the mutatingwebhook at

pipelines/backend/src/cache/server/mutation.go

Lines 151 to 155 in 1db9db5

	dummyContainer := corev1.Container{
	Name: "main",
	Image: image,
	Command: []string{`echo`, `"This step output is taken from cache."`},
	}

I used https://github.com/pantheon-systems/cassandra-operator/blob/735de0001e9d23ea0bf4a79c6b51f4ccbe95777d/pkg/resource/cassandra_pod.go#L90 as reference

[google-oss-robot]

Hi @juliusvonkohout. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[juliusvonkohout]

@Ark-kun
@rui5i
can you take a look at this fix?

[juliusvonkohout]

@Bobgy what do you think?

[Bobgy]

/cc @capri-xiyue
What do you think?

/lgtm

[capri-xiyue]

Is it possible to read the Resources requests and requirements from kubeflow profile quotas like configmap https://github.com/kubeflow/pipelines/pull/5695/files#diff-61f22a36206e85146e61ed6d59d5a0636acc9b4e95b4f97f647727a02ad20710R2?

[juliusvonkohout]

@capri-xiyue we could mount the key "executor" of the workflow-controller-configmap as we do mount pipeline-install-config, but then we would have to parse the text and I do not see the reason for that. These two numbers are not that strongly related one is for real Argo preparation and to satisfy kubeflow profile quota restrictions, the other is just for pulling the cached value from minio an satisfying the kubeflow profile quota requirements. I can also change it to 32Mi manually for more "consistency"

[capri-xiyue]

/lgtm
/approve

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: capri-xiyue

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:

• backend/OWNERS [capri-xiyue]

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