openshift-pipelines/pipeline-service

Kcp-in-a-pod - towards more generic and synchronized manifests

Closed this issue · 3 comments

Parent comment - here.

Tasks -

  • Split the ckcp deployment into two applications:
    - Operator installation through subscription
    - Next steps as an Application with presync hook waiting for the API to be available (with timeout).

predecessor - #68

@ramessesii2 Is this issue worked on? I believe the first one is done. Not so sure about the presync hook. Do we need that anymore?

Hey @bnallapeta, yes, part of this issue i.e., Operator installation through subscription and deployment through argo cd is done. Presync hook seems good to have for ckcp but not important right now.

KCP being out of the picture, I'm closing this issue as deprecated.