Doc - nice to have - diagram for relationship between repository, installed packages and running software from a namespaces perspective

[kcoriordan]

@cormachogan feedback
In relation to Work with packages doc

Regarding the following statement: "This does not determine which namespace(s) the software will run in.", would it be worth discussing the relationship between repository, installed packages and running software from a namespaces perspective, and have a dedicated diagram just for that. I feel this is the area that most readers will get tripped up.

[joshrosso]

This existing image attempts to show this relationship.

Does it not satisfy this? If no, how can we improve it?

[cormachogan]

Hey @joshrosso - so I was thinking of an even simpler block diagram to get started, where the package is pulled from an external repo into a particular namespace in the cluster to make it "available" for install, and then when it is actually installed, it's components are placed in another namespace as per the install command. So a simplified diagram that precedes this more detailed diagram.

[joshrosso]

@cormachogan want to take a stab at this diagram?

[cormachogan]

Yes - would be happy to @joshrosso

[cormachogan]

pkgs.pptx

My thoughts were along the lines of what I have put in this presentation. Thoughts @joshrosso @kcoriordan ?

[cormachogan]

@joshrosso - I think much of the package confusion is stemming from this #1964

[cormachogan]

I spent more time on this today. I think the whole thing could be synopised as:

1. If you install the package repository in any namespace other than tanzu-package-repo-global, then the package install resources must also be installed in the same namespace. This includes the default namespace, which is where a repository is installed, by default. Package deployment objects may still be deployed to another namespace. This is controlled via the package schema and can be modified by passing in a namespace via the values file at package install time.

2. If you install the package repository in the namespace tanzu-package-repo-global, then the package install resources may be placed in a different namespace to the repository namespace. This is handled via the --namespace command during package install. Package deployment objects may still be deployed to another namespace. This is controlled via the package schema and can be modified by passing in a namespace via the values file at package install time.
   pkgs-revisited.pptx

I have added an updated PPT as well to capture my testing.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.