Tanzu Framework v0.25.3
Tanzu CLI Installation Instructions
If you are installing Tanzu CLI using the artifacts published as part of this release, please follow the instructions.
Changes by Kind
Feature
- Added discovery source for TMC.
Fixed fetching artifacts over http to handle large file reads by processing chunks at a time. (#2950, @pgandigesang)
Bug or Regression
Miscellaneous
-
Bump kapp-controller to 0.38.5 for release-0.25 (#3540, @haoranleo)
-
Currently, all CLI plugins are specific to the Kubernetes context. As more services like TMC add plugins, there is some room for confusion as there is name collision between the plugins. To make the user experience very explicit, we are adding the target to the command invocation.
With this change, the Tanzu CLI supports two targets (context types):
kubernetes
,mission-control
. This is currently backwards compatible, i.e., the plugins are still available at the root level. In addition to that, we have all the contextual plugins grouped under their corresponding targets.Note: This is currently behind a feature flag. To enable the flag please run tanzu config set features.global.context-target true and then run
tanzu init
once after the upgrade.Please find some examples below:
- TKG workload cluster plugin:
Without target grouping (a TKG management cluster is set as the current active server)
~ tanzu cluster
With target grouping
~ tanzu kubernetes cluster
- TMC workload cluster plugin:
Without target grouping (a TMC server is set as the current active server)
~ tanzu cluster
With target grouping
~ tanzu mission-control cluster
(#3126, @giri-varma) -
Currently, the Tanzu CLI supports storing authentication information on a per server basis (management cluster). This information is created using the login plugin and can be managed using the config server command in the core CLI. As we add more server types like a workload cluster, Tanzu Mission Control endpoint, etc. we need a consistent mechanism to manage the configuration for every server or rather for every context.
Also, we need to move away from the notion of server to contexts. To clarify, a server is just a remote endpoint that can be accessed via the Tanzu CLI (or its plugins). A context would include a server endpoint and any related client side configurations like default output format, feature flags enabled, etc. This can also be extended in future to support a local environment without any server if needed.
Hence, added a context command as part of the core CLI like below to create and manage contexts in the CLI.
Note: This is currently behind a feature flag. To enable the flag please run tanzu config set features.global.context-target true
Migration notes:
- CLI users should start using the
context
command instead of thelogin
command. - Plugin developers should use the
config.GetContext
methods in the core CLI library instead ofconfig.GetServer
when looking for server information.
~ tanzu context -h
Configure and manage contexts for the Tanzu CLIUsage:
tanzu context [command]Aliases:
context, ctx, contextsAvailable Commands:
create Create a Tanzu CLI context
delete Delete a context from the config
get Display a context from the config
list List contexts
use Make a context as the current active context for its typeFlags:
-h, --help help for contextUse "tanzu context [command] --help" for more information about a command. (#2202, @giri-varma)
- CLI users should start using the
-
Fixes UI bug that inserted trailing comma in cluster labels and annotations (#3662, @miclettej)
-
Users can now configure the NSX ALB controller with the same ALB resource name across multiple clouds. (#3721, @XudongLiuHarold)
Dependencies
Added
Nothing has changed.
Changed
- github.com/stretchr/objx: v0.2.0 → v0.4.0
- github.com/stretchr/testify: v1.7.1 → v1.8.0
- gopkg.in/yaml.v3: 496545a → v3.0.1
- sigs.k8s.io/cluster-api-provider-vsphere: v1.3.1 → v1.3.5
Removed
Nothing has changed.
Full Changelog: v0.25.1...v0.25.3