[TASK] Agree on future of components/example-notebook-servers presently in notebooks-v1

[andyatmiami]

Certification

• I certify I am an Epic Owner for Kubeflow Notebooks 2.0 and expected to create planning-related issues.

Description

Before creating the first release for the notebooks-v1 branch, we need to ensure that we are aligned on a couple of details specifically around components/example-notebooks-servers that can affect future releases as well.

Specifically, before the first release is published from kubeflow/notebooks notebooks-v1 we'll need to make sure we've agreed on:

• Should example-server-images be its own repo or remain in the notebooks-v1 branch?
• Should we continue to publish to ghcr.io/kubeflow/kubeflow or move to ghcr.io/kubeflow/notebooks or move to something else entirely if we decide to migrate this folder again to its own repo?
• Which docker tag should we use for the first release?

The above will be quite important to agree on before the release, as it will dictate the future releases as well.

cc: @thesuperzapper @juliusvonkohout @kimwnasptd

Acceptance Criteria

• Consensus reached (explicitly or via lazy consensus) on what repo/branch example-notebook-servers should live long-term
• Consensus reached (explicitly or via lazy consensus) on image registry for example-notebook-servers
• Consensus reached (explicitly or via lazy consensus) on docker tags for example-notebook-servers

[juliusvonkohout]

@andyatmiami did you raise this in the notebooks call? cc also @ederign

I do not care much about the tag and i think that "move to ghcr.io/kubeflow/notebooks" would be good.

[andyatmiami]

I have raised the need to discuss - but we haven't really/actually discussed yet in a strict/formal capacity to try to drive to a decision...

appreciate you weighing in! even "i don't care" is a good feedback/indicator - so we know "your voice is heard".

will make sure any proposals/decisions (once we have them) are captured on this issue!

[thesuperzapper]

Let's use the existing ghcr.io/kubeflow/kubeflow/notebook-servers image registries for new updates going forwards out of the kubeflow/notebooks repo (which will become the new "authoritative" source for the example notebook servers).

To this end, I have updated the permissions on the notebook-servers registries so that only kubeflow/notebooks GitHub Actions can push to it (so we don't accidentally make new tags from the old kubeflow/kubeflow repo).

[liavweiss]

Hey, I have created this PR #640 for this issue.

[andyatmiami]

/close

Based on:

• @thesuperzapper 's input
• age of issue without others voicing dissenting opinions (as @juliusvonkohout mentioned he did not care much )

I am going to consider this issue resolved - with the following comment being the decision moving forward:

• [TASK] Agree on future of components/example-notebook-servers presently in notebooks-v1 #585 (comment)