Tanzu Framework v0.11.2

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

• Add the ability to have an init container to inject core DNS IP into /etc/resolv.conf for Kapp-Controller package. (#1328, @blc1996)

Bug or Regression

• Fix tanzu init and tanzu update command not respecting context-aware-cli-for-plugins feature flag (#1412, @anujc25)
• Fix bug to enable setting up proxy for cap* infrastructure controllers. (#1216, @saimanoj01)
• Fix cluster upgrade failure error for proxied environment related to config variable TKG_HTTP_PROXY_ENABLED not set (#1469, @anujc25)
• Fix error/warning displayed when CLIPlugin CRD is not installed with tanzu plugin commands (#1393, @anujc25)
• Fix the issue where where cluster upgrade doesn't timeout and stuck indefinitely (#1229, @prkalle)
• Fixed upgrade exits prematurely when upgrade does not involve a change in Kubernetes version (#1283, @anujc25)
• Made CLI backward compatible by supporting legacy directory structure with tanzu plugin install --local command (#1486, @anujc25)

Miscellaneous

• Add extra read only IAM permissions to support Tanzu Mission Control (#1343, @pydctw)
• Adds annotation (edition: ${EDITION}) to management cluster.
  Skip upgrade standard-package-repo addon when edition does not support it. (#1787, @navidshaikh)
• Allow only trusted registries when installing plugins from OCI source
  Fixed issue regarding installing plugins on internet restricted environment from OCI source (#1500, @anujc25)
• Bump kapp-controller version to 0.30.0 (#1197, @danniel1205)
• Creates namespace prior to package metadata check. This causes the package metadata check not fail as a result of non-existing namespace, specifically for packages made available as part of adding the package repository to a global namespace. (#1263, @maralavi)
• Fix tanzu config set env command to not be namespace-based (#1215, @anujc25)
• Fix issue with duplicate network paths in vSphere (#1489, @saimanoj01)
• Fixed issue with autoscaler deployment on clusters using k8s version v1.22. (#1390, @saimanoj01)
• Fixed: TKR status not being updated after mgmt cluster upgrade (#1520, @imikushin)
• Fixes a rare issue where cluster machines would be incorrectly rotated when performing an upgrade where the only change to the cluster was the name or path of the VM template. (#1495, @tenczar)
• Fixes the bug that cause segmentation fault on trying to access non existing SecretExport object (#1291, @maralavi)
• Increases kube-vip timeouts during the upgrade process (#1231, @saji-pivotal)
• Introduces ANTREA_DISABLE_UDP_TUNNEL_OFFLOAD for UDP tunnel offload feature configuration. (#1374, @knabben)
• Loosens version check when creating workload clusters. Management cluster and cli need not match in patch version. (#1501, @tenczar)
• Support for CSI 2.4.0 (#1210, @blc1996)
• Update CAPV to version v1.0.2 (#1373, @srm09)
• Updated ytt defaults to disable outbound load balancers when creating private clusters on Azure. (#1301, @saimanoj01)
• Validates filepaths to ensure that an archive cannot be unzipped outside the current directory (#1312, @saji-pivotal)

Dependencies

Added

Nothing has changed.

Changed

• sigs.k8s.io/cluster-api-provider-azure: v1.0.0 → v1.0.1
• sigs.k8s.io/cluster-api-provider-vsphere: v1.0.1 → v1.0.2
• sigs.k8s.io/cluster-api/test: v1.0.0 → v1.0.1
• sigs.k8s.io/cluster-api: v1.0.0 → v1.0.1
• sigs.k8s.io/controller-runtime: v0.10.2 → v0.10.3

Removed

Nothing has changed.

For detailed changes in release v0.11, please refer to v0.11.0 release notes and v0.11.1 release notes

Full Changelog: v0.11.1...v0.11.2