Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

[Docs] [](/docs/latest/getting-started-standalone/) Adding the TCE Package Repository command should refer to v0.9.2 #3084

Closed
kartiklunkad26 opened this issue Feb 8, 2022 · 5 comments · Fixed by #3086
Assignees
Labels
kind/docs A change in documentation
Milestone

Comments

@kartiklunkad26
Copy link
Contributor

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

@kartiklunkad26 kartiklunkad26 added kind/docs A change in documentation triage/needs-triage Needs triage by TCE maintainers labels Feb 8, 2022
@kcoriordan
Copy link
Contributor

kcoriordan commented Feb 8, 2022

I wasn't aware of this, so the package repository should be = v0.9.2
but the latest TCE release remains at v0.9.1

PS C:\test-k\tce-windows-amd64-v0.10.0-rc.3\tce-windows-amd64-v0.10.0-rc.3> tanzu package repository add tce-repo --url projects.registry.vmware.com/tce/main:0.9.2 --namespace tanzu-package-repo-global

Updated package repository 'tce-repo' in namespace 'tanzu-package-repo-global'
PS C:\test-k\tce-windows-amd64-v0.10.0-rc.3\tce-windows-amd64-v0.10.0-rc.3> tanzu package repository list --namespace tanzu-package-repo-global

  ←[1mNAME    ←[0m  ←[1mREPOSITORY                           ←[0m  ←[1mTAG  ←[0m  ←[1mSTATUS             ←[0m  ←[1mDETAILS←[0m
  tce-repo  projects.registry.vmware.com/tce/main  0.9.2  Reconcile succeeded
PS C:\test-k\tce-windows-amd64-v0.10.0-rc.3\tce-windows-amd64-v0.10.0-rc.3> tanzu package available list

  ←[1mNAME                                         ←[0m  ←[1mDISPLAY-NAME      ←[0m  ←[1mSHORT-DESCRIPTION                                                                                                           ←[0m  ←[1mLATEST-VERSION←[0m
  cert-manager.community.tanzu.vmware.com        cert-manager        Certificate management                                                                                                        1.6.1
  contour.community.tanzu.vmware.com             contour             An ingress controller                                                                                                         1.19.1
  external-dns.community.tanzu.vmware.com        external-dns        This package provides DNS synchronization functionality.                                                                      0.10.0
  fluent-bit.community.tanzu.vmware.com          fluent-bit          Fluent Bit is a fast Log Processor and Forwarder                                                                              1.7.5
  gatekeeper.community.tanzu.vmware.com          gatekeeper          policy management                                                                                                             3.7.0
  grafana.community.tanzu.vmware.com             grafana             Visualization and analytics software                                                                                          7.5.7
  harbor.community.tanzu.vmware.com              harbor              OCI Registry                                                                                                                  2.3.3
  knative-serving.community.tanzu.vmware.com     knative-serving     Knative Serving builds on Kubernetes to support deploying and serving of applications and functions as serverless containers  1.0.0
  kpack.community.tanzu.vmware.com               kpack               kpack builds application source code into OCI compliant images using Cloud Native Buildpacks                                  0.5.0
  local-path-storage.community.tanzu.vmware.com  local-path-storage  This package provides local path node storage and primarily supports RWO AccessMode.                                          0.0.20
  multus-cni.community.tanzu.vmware.com          multus-cni          This package provides the ability for enabling attaching multiple network interfaces to pods in Kubernetes                    3.7.1
  prometheus.community.tanzu.vmware.com          prometheus          A time series database for your metrics                                                                                       2.27.0
  velero.community.tanzu.vmware.com              velero              Disaster recovery capabilities                                                                                                1.7.1
  whereabouts.community.tanzu.vmware.com         whereabouts         A CNI IPAM plugin that assigns IP addresses cluster-wide                                                                      0.5.0`
`

@stmcginnis
Copy link
Contributor

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?

@kcoriordan
Copy link
Contributor

kcoriordan commented Feb 8, 2022

@stmcginnis
OK, I can add a variable for this
When v0.10.0 goes out, will the package repo change to 0.10.0

@kcoriordan kcoriordan self-assigned this Feb 8, 2022
@kcoriordan kcoriordan removed the triage/needs-triage Needs triage by TCE maintainers label Feb 8, 2022
@kcoriordan kcoriordan added this to the v0.10.0 milestone Feb 8, 2022
@stmcginnis
Copy link
Contributor

When v0.10.0 goes out, will the package repo change to 0.10.0

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.

@kcoriordan
Copy link
Contributor

OK so I created a variable and this should probably get updated by automation when the repo is tagged for final GA?
and if we need a different pkg repo version between releases, we can update the pkg-repo variable manually

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/docs A change in documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants