-
Notifications
You must be signed in to change notification settings - Fork 307
[Docs] [](/docs/latest/getting-started-standalone/) Adding the TCE Package Repository command should refer to v0.9.2 #3084
Comments
I wasn't aware of this, so the package repository should be = v0.9.2
|
Yeah, we needed to release a new package repo update to pick up kpack, but that didn't correspond to a full TCE release. So there is a newer package repo. Is there a way we can set a docs variable to pick this up that would default to be the same as the normal release version, but would allow us to update it to something else if needed? |
@stmcginnis |
Yes, I believe that is the plan. But if we find some need to update the available packages between then and v0.11.0, we would have the same situation and end up with a 0.10.1 package repo version. |
OK so I created a variable and this should probably get updated by automation when the repo is tagged for final GA? |
Description
The docs refer to v0.9.1 for the TCE Package Repository. This means kpack won't be available for installation.
Location
https://tanzucommunityedition.io/docs/latest/getting-started-standalone/#creating-clusters
In the section of Installing a Package
Install the Tanzu Community Edition package repository into the tanzu-package-repo-global namespace.
tanzu package repository add tce-repo --url projects.registry.vmware.com/tce/main:0.9.1 --namespace tanzu-package-repo-global
Additional Context
The text was updated successfully, but these errors were encountered: