Enable Metadata Writer for KFP

[jlewi]

See this comment
#796 (comment)

KFP and metadata need to be configured correctly to enable the metadata writer service.

/cc @elikatsis @Ark-kun

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
feature	0.70

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[jlewi]

@Ark-kun any interest in picking this up?

Some relevant links
https://github.com/kubeflow/pipelines/tree/master/backend/metadata_writer

[elikatsis]

@jlewi We first need to merge kubeflow/pipelines#3108

[Ark-kun]

/cc @dushyanthsc

[jlewi]

@elikatsis @dushyanthsc any update on this?

[elikatsis]

Hi @jlewi,

I believe MetadataWriter implementation as well as the related KFP manifests are compatible with KF manifests. So it should be easy to extend these manifests to deploy metadata writer.

I'll let @dushyanthsc or @rmgogogo verify.

[dushyanthsc]

We updated the manifest to be consistent. Is there anything else required to change on the Metadata (gRPC) deployments to enable metadata-writer @Ark-kun ?

[jlewi]

Downgrading to p2 and removing from KF 1.1. because it doesn't look like we have a clear owner so it doesn't seem like its going to get completed.

/cc @aronchick @karlschriek

[Ark-kun]

Is there anything else required to change on the Metadata (gRPC) deployments to enable metadata-writer @Ark-kun ?

No. Metadata Writer is standalone and should be compatible with the rest of the deployments (after the GRPC vs. HTTP service names were fixed).

[Ark-kun]

@jlewi I think we just need to add the Metadata Writer deployment (deployment, SA, role, binding) manifests to KF.

[Ark-kun]

/cc @rmgogogo @Bobgy

[Ark-kun]

Looks like #1248 fixes this issue.