Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-5393

Create a fork of sail operator in our organization

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • OSSM 3.0-TP1
    • None
    • Sail Operator
    • None

      Our fork needs to have a minimal set of changes compared to the upstream repository. Ideally, we can keep these changes in a separate file so we don't experience git conflicts.

      Acceptance Criteria:

      • it's possible to switch between upstream and downstream files when building manifests (e.g. using env variables VERSIONS_FILE, VALUES_FILE, or Makefile.overrides)
      • set product operator version to 3.0.0
      • Setup a sync job with upstream (e.g. for each commit? daily?)
      • new files must not break updates done by Automator
      • custom values.yaml for CSV generation
      • cpaas is configured to use generated downstream manifests from the fork repo

              jsantana@redhat.com Jonh Wendell
              jsantana@redhat.com Jonh Wendell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: