Release Notes

Note: As of v1.8, Enterprise PKS has been renamed to VMware Tanzu Kubernetes Grid Integrated Edition. Some screenshots in this documentation do not yet reflect the change.

Page last updated:

This topic contains release notes for Tanzu Kubernetes Grid Integrated Edition (TKGI) v1.8.

TKGI v1.8.2

Release Date: October 1, 2020

Product Snapshot

Release Details
Version v1.8.2
Release date October 1, 2020
Component Version
Kubernetes v1.17.11+vmware.1
CoreDNS v1.6.5+vmware.7
Docker v19.03.5
etcd v3.4.3
Metrics Server v0.3.6
NCP v3.0.1.2
On-Demand Broker v0.38.0
Percona XtraDB Cluster (PXC) v0.22.0
UAA v74.5.18
Compatibilities Versions
Ops Manager See VMware Tanzu Network
Xenial stemcells* See VMware Tanzu Network
Windows stemcells vSphere v7.0: v2019.15
vSphere v6.7 or v6.5: v2019.15 and later
Backup and Restore SDK v1.18.0
vSphere See VMware Product Interoperability Matrices
CNS for vSphere v2.0, v1.0.2
NSX-T v3.0.1.1 (v3.0.1 EP1), v2.5.2
Harbor v1.10.3

* See TKGI v1.9 With NSX-T Not Compatible With Xenial Stemcells 621.85.

Upgrade Path

The supported upgrade paths to TKGI v1.8.2 are from Tanzu Kubernetes Grid Integrated Edition v1.7.0 and later.

Features

This section describes new features and changes in Tanzu Kubernetes Grid Integrated Edition v1.8.2.

  • Bumps Kubernetes to v1.17.11+vmware.1.
  • Bumps UAA to v74.5.18.
  • [Bug Fix] Adds syslog_forwarder to the Tanzu Kubernetes Grid Integrated Edition database VM.
  • [Bug Fix] Now creates the observability-manager pod with a valid image name.

Known Issues

Except where noted, Tanzu Kubernetes Grid Integrated Edition v1.8.2 has the same known issues as Tanzu Kubernetes Grid Integrated Edition v1.8.0. See Known Issues in Tanzu Kubernetes Grid Integrated Edition v1.8.0.

TKGI v1.8.1

Release Date: July 17, 2020

Product Snapshot

Release Details
Version v1.8.1
Release date July 17, 2020
Component Version
Kubernetes v1.17.8+vmware.1
CoreDNS v1.6.2
Docker v19.03.5
etcd v3.4.3
Metrics Server v0.3.6
NCP v3.0.1.2
On-Demand Broker v0.38.0
Percona XtraDB Cluster (PXC) v0.22.0
UAA v74.5.15
Compatibilities Versions
Ops Manager AWS, Azure, GCP, and vSphere v6.7 or v6.5: See VMware Tanzu Network
vSphere v7.0: Ops Manager v2.10.1+, v2.9.3+ (v2.9.5+ with VDS*)
Xenial stemcells* See VMware Tanzu Network
Windows stemcells vSphere v7.0: v2019.15
vSphere v6.7 or v6.5: v2019.15 and later
Backup and Restore SDK v1.18.0
vSphere See VMware Product Interoperability Matrices
CNS for vSphere v2.0, v1.0.2
NSX-T v3.0.1.1 (v3.0.1 EP1), v2.5.2, v2.5.1, v2.5.0
Harbor v2.0.1, v1.10.3

Upgrade Path

The supported upgrade paths to TKGI v1.8.1 are from Tanzu Kubernetes Grid Integrated Edition v1.7.0 and later.

Features

This section describes new features and changes in Tanzu Kubernetes Grid Integrated Edition v1.8.1.

  • Bumps Kubernetes to v1.17.8+vmware.1.
  • Bumps NCP to v3.0.1.2.
  • [Issue Fix] NCP bump and NSX-T express patch remove incompatibility with Xenial Stemcells 621.76+ and Ops Manager v2.9.6.
    • Because TKGI v1.8.0 is incompatible with 621.76+ stemcells, you must upgrade TKGI to v1.8.1 and update all clusters before upgrading stemcells to 621.76+.
  • [Issue Fix] NCP bump and NSX-T express patch introduce beta support for VDS under specific conditions.
  • [Security Fix] Kubernetes bump fixes the following CVEs:
    • CVE-2020-8558: node setting allows for neighboring hosts to bypass localhost boundary.
    • CVE-2020-8559: privilege escalation from compromised node to cluster.
  • Support for vSphere v7.0 Virtual Distributed Switch (VDS). See NSX-T support on VDS 7.0 in the NSX Data Center 3.0 Release Notes to learn more about NSX-T v3.0 integration with VDS v7 and the considerations for using VDS v7 for converged traffic. TKGI with VDS requirements:
    • Ops Manager v2.9.5 and later.
    • NSX-T v3.0.1.1 (v3.0.1 EP1) or later.
    • New installations of TKGI v1.8.1 and NSX-T 3.0.1.1. You cannot migrate existing NSX-T infrastructure for TKGI from N-VDS to VDS.
    • With a single VDS per TKGI instance, if you are installing TKGI using EPMC. Note that this limitation does not exist when TKGI is deployed with Ops Manager.

Known Issues

Except where noted, known issues in Tanzu Kubernetes Grid Integrated Edition v1.8.1 are also in Tanzu Kubernetes Grid Integrated Edition v1.8.0. See Known Issues in Tanzu Kubernetes Grid Integrated Edition v1.8.0.

TKGI v1.8.0

Release Date: June 30, 2020

Product Snapshot

Release Details
Version v1.8.0
Release date June 30, 2020
Component Version
Kubernetes v1.17.5
CoreDNS v1.6.2
Docker v19.03.5
etcd v3.4.3
Metrics Server v0.3.6
NCP v3.0.1
On-Demand Broker v0.38.0
Percona XtraDB Cluster (PXC) v0.22.0
UAA v74.5.15
Compatibilities Versions
Ops Manager AWS, Azure, GCP: See VMware Tanzu Network
vSphere v7.0: Ops Manager v2.9.3 - v2.9.5*
vSphere v6.7 or v6.5: Ops Manager v2.9.3 - v2.9.5*, v2.8.2+, v2.7.15+
Xenial stemcells* See VMware Tanzu Network
Windows stemcells vSphere v7.0: v2019.15
vSphere v6.7 or v6.5: v2019.15 and later
Backup and Restore SDK v1.18.0
vSphere** See VMware Product Interoperability Matrices
CNS for vSphere v1.0.2
NSX-T v3.0***, v2.5.1, v2.5.0
Harbor v2.0.1, v1.10.3

* See TKGI v1.8 With NSX-T v3.0 Not Compatible With Xenial Stemcells 621.76+ and Ops Manager v2.9.6.

** Excluding VCF 4; see VCF 4 and VDS v7 Not Supported in TKGI v1.8.0.

*** VMware recommends NSX-T v3.0.1.1 (v3.0.1 EP1) or later for NSX-T v3.0 integration. Upgrading to earlier versions of NSX-T v3.0 is not recommended for production or large-scale TKGI environments. For more information about NSX-T v3.0 support, see NSX-T v3.0 Compatibility below.

Upgrade Path

The supported upgrade paths to Tanzu Kubernetes Grid Integrated Edition v1.8.0 are from TKGI v1.7.0 and later.

Note: VMware recommends upgrading to TKGI v1.8.1 or later, not upgrading to v1.8.0.

Features

This section describes new features and changes in VMware Tanzu Kubernetes Grid Integrated Edition v1.8.0.

Enterprise PKS Renamed to Tanzu Kubernetes Grid Integrated Edition

Enterprise PKS has been renamed to Tanzu Kubernetes Grid Integrated Edition (TKGI).

What has changed:

  • The Tanzu Kubernetes Grid Integrated Edition v1.8 tile uses the new name.
  • Tanzu Kubernetes Grid Integrated Edition v1.8 includes two downloads of the CLI, the TKGI CLI and PKS CLI. See PKS CLI Renamed to TKGI CLI below.

What has not changed:

  • Internal components continue to use the old name and its alternatives, such as PKS, pks, and pivotal-container-service. This includes, but is not limited to, BOSH names, UAA roles, and text strings containing the product name in TKGI components and TKGI-provisioned clusters.

If you intend to continue using the PKS CLI in TKGI v1.8, no action is required. However, future releases of TKGI will deprecate and remove the PKS CLI.

PKS CLI Renamed to TKGI CLI

To support the product name change, Tanzu Kubernetes Grid Integrated Edition v1.8 is distributed with a TKGI CLI in addition to a PKS CLI.

Both CLIs work identically and accept the same commands and arguments. To run a TKGI CLI command, substitute tkgi where you previously used pks. For more information, see TKGI CLI.

To download the TKGI CLI or the PKS CLI, see VMware Tanzu Network.

vSphere v7 Compatibility

TKGI v1.8 can run on vSphere v7.

NSX-T v3.0 Compatibility

On vSphere, TKGI can run with NSX-T v3.0 container networking with NSX-T v3.0.1.1 (v3.0.1 EP1) or later.

Upgrading TKGI to NSX-T v3.0.1 requires you to apply the v3.0.1 EP1 Express Patch to the NSX-T upgrade.

Warning: Intermittent upgrade failures and scale problems may occur if you upgrade to NSX-T v3.0.0, or upgrade to NSX-T v3.0.1 without applying the Express Patch.

TKGI Control Plane and API

  • The TKGI API VM no longer stores a copy of the control plane database that the v1.7 upgrade migrated to the Database VM. This deletion frees internal memory in the TKGI API VM. As a result, users may notice improved control plane performance.

  • The PKS 1.7.x Upgrade - MySQL Clone errand errand has been removed from the Errands pane in the TKGI tile.

Kubernetes Control Plane

  • On Azure, TKGI supports disabling the creation of a default outbound SNAT rule for clusters. See Kubernetes Cloud Provider for how to disable the default SNAT rule.

TKGI Monitoring and Logging

  • All TKGI components use TLS v1.2 with strong ciphers, including the metrics-server component. sslscan on a metrics-server over port 443 now reports only TLS v1.2+ ciphers.

Customer Experience Improvement Program (CEIP) and Telemetry

  • The legacy Telemetry DB has been removed from the TKGI Database.

Component Updates

The following components have been updated:

  • Bumps Kubernetes to v1.17.5.
  • Bumps NCP to v3.0.1.
  • Bumps UAA to v74.5.15.

Bug Fixes

TKGI v1.8.0 includes the following bug fixes:

  • tkgi tasks returns valid output for all clusters.
  • tkgi upgrade-cluster errand no longer times out when stopping dockerd processes.
  • tkgi get-credentials works for clusters that have not been upgraded.
  • tkgi update-cluster retains the compute_profile value when changing settings for clusters created with a compute Profile.

Known Issues

TKGI v1.8.0 has the following known issues:

Error: Could Not Execute “Apply-Changes” in Azure Environment

Symptom

After clicking Apply Changes on the TKGI tile in an Azure environment, you experience an error ’…could not execute “apply-changes”…’ with either of the following descriptions:

  • {“errors”:{“base”:[“undefined method ‘location’ for nil:NilClass”]}}
  • FailedError.new(“Resource Groups in region ’#{location}’ do not support Availability Zones”))

For example:

INFO | 2020-09-21 03:46:49 +0000 | Vessel::Workflows::Installer#run | Install product (apply changes)
2020/09/21 03:47:02 could not execute "apply-changes": installation failed to trigger: request failed: unexpected response from /api/v0/installations:
HTTP/1.1 500 Internal Server Error
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Mon, 21 Sep 2020 17:51:50 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: f5fc99c1-21a7-45c3-7f39
X-Runtime: 9.905591
X-Xss-Protection: 1; mode=block

44
{"errors":{"base":["undefined method `location' for nil:NilClass"]}}
0

Explanation

The Azure CPI endpoint used by Ops Manager has been changed and your installed version of Ops Manager is not compatible with the new endpoint.

Workaround

Run the following Ops Manager CLI command:

om --skip-ssl-validation --username USERNAME --password PASSWORD --target https://OPSMAN-API curl --silent --path /api/v0/staged/director/verifiers/install_time/IaasConfigurationVerifier -x PUT -d '{ "enabled": false }'

Where:

  • USERNAME is the account to use to run Ops Manager API commands.
  • PASSWORD is the password for the account.
  • OPSMAN-API is the IP address for the Ops Manager API

For more information, see Error 'undefined method location’ is received when running Apply Change on Azure in the VMware Tanzu Knowledge Base.

Loss of Network Connectivity While Upgrading Stateful Kubernetes Clusters

Stateful sets with attached persistent storage on TKGI on vSphere with NSX-T might lose network connectivity while upgrading the set’s Kubernetes clusters from TKGI v1.7 to TKGI v1.8. If a stateful set loses network connectivity, the set’s workloads remain unavailable until all nodes of the cluster have been upgraded.

TKGI v1.8.0 With NSX-T v3.0 Not Compatible With Xenial Stemcells 621.76+ and Ops Manager v2.9.6

This issue is fixed in TKGI v1.8.1.

TKGI with NSX-T v3.0 is compatible with Linux Ubuntu Xenial stemcell v621.75, but not with stemcell versions v621.76 and later.

TKGI v1.8.0 on vSphere with NSX-T is compatible with Ops Manager v2.9.3 - v2.9.5. TKGI v1.8.0 on vSphere with NSX-T is incompatible with Ops Manager v2.9.6 because that Ops Manager version uses Xenial stemcell v621.76.

VCF 4 and VDS v7 Not Supported in TKGI v1.8.0

For installations on vSphere v7 with NSX-T v3.0 integration, TKGI v1.8 supports only N-VDS for NSX-T traffic. It does not support:

  • VDS v7 using the same VDS for both vSphere and NSX-T traffic
  • VMware Cloud Foundation (VCF) v4.x, which uses only VDS mode with NSX-T v3.0

In TKGI v1.8.1, VDS support is beta under certain conditions.

For more information, see Configure vSphere Networking for ESXi Hosts in Installing and Configuring NSX-T Data Center v3.0 for Tanzu Kubernetes Grid Integrated Edition.

TKGI v1.8 (Windows) on vSphere Not Compatible with Ops Manager v2.9

TKGI v1.8 installations with Windows worker-based Kubernetes clusters on vSphere (Flannel) are not compatible with Ops Manager v2.9. If you do not intend to deploy and run Windows worker-based Kubernetes clusters, you can use Ops Manager v2.9 with TKGI v1.8.

For Ops Manager compatibility information, see VMware Tanzu Network.

Pinging Windows Workers Does Not Work

TKGI-provisioned Windows workers inherit a Kubernetes limitation that prevents outbound ICMP communication from workers. As a result, pinging Windows workers does not work.

For information about this limitation, see Limitations > Networking in the Windows in Kubernetes documentation.

TMC Integration Not Supported on GCP

TKGI on Google Cloud Platform (GCP) does not support Tanzu Mission Control integration, which is configured in the Tanzu Kubernetes Grid Integrated Edition tile > the Tanzu Mission Control (Experimental) pane.

If you intend to run TKGI v1.8 on GCP, skip this pane when configuring the Tanzu Kubernetes Grid Integrated Edition tile.

502 Bad Gateway After OIDC Login

Symptom

You experience a “502 Bad Gateway” error from the NSX load balancer after you log in to OIDC.

Explanation

A large response header has exceeded your NSX-T load balancer maximum response header size. The default maximum response header size is 10,240 characters and should be resized to 50,000.

Workaround

If you experience this issue, manually reconfigure your NSX-T request_header_size and response_header_size to 50,000 characters. For information about configuring NSX-T default header sizes, see OIDC Response Header Overflow in the Knowledge Base.

One Plan ID Longer than Other Plan IDs

Symptom

One of your plan IDs is one character longer than your other plan IDs.

Explanation

In TKGI, each plan has a unique plan ID. A plan ID is normally a UUID consisting of 32 alphanumeric characters and 4 hyphens. However, the Plan 4 ID consists of 33 alphanumeric characters and 4 hyphens.

Solution

You can safely configure and use Plan 4. The length of the Plan 4 ID does not affect the functionality of Plan 4 clusters.

If you require all plan IDs to have identical length, do not activate or use Plan 4.

NSX-T Pre-Check Errand Fails Due to Edge Node Configuration

Symptom

You have configured your NSX-T Edge Node VM as medium size, and the NSX-T Pre-Check Errand fails with the following error: “ERROR: NSX-T Precheck failed due to Edge Node … no of cpu cores is less than 8”.

Explanation

The NSX-T Pre-Check Errand is erroneously returning the “cpu cores is less than 8” error.

Solution

You can safely configure your NSX-T Edge Node VMs as medium size and ignore the error.

Difficulty Changing Proxy for Windows Workers

You must configure a global proxy in the Tanzu Kubernetes Grid Integrated Edition tile > Networking pane before you create any Windows workers that use the proxy.

You cannot change the proxy configuration for Windows workers in an existing cluster.

Character Limitations in HTTP Proxy Password

For vSphere with NSX-T, the HTTP Proxy password field does not support the following special characters: & or ;.

Kubernetes Clusters With Xenial Stemcell v621.85 Fail After Upgrading TKGI on vSphere With NSX-T to TKGI v1.8 and Later

Symptom

After you upgrade to TKGI on vSphere with NSX-T v1.8 and later, TKGI-provisioned Kubernetes clusters with Xenial Stemcell v621.85 fail to start. The cluster start failure log includes the following:

Error: Action Failed get_task: Task ... result: Compiling package openvswitch: 
Running packaging script: Running packaging script: Command exited with 2;

Xenial Stemcell v621.85 is installed by default when installing Ops Manager v2.8.15.

Workaround

If you experience this issue, manually revert the stemcell to an earlier compatible version. For information about reverting stemcells, see How to revert a stemcell in TKGI to prevent OVS compilation issues in the Knowledge Base.

TKGI Management Console 1.8.2

Release Date: October 01, 2020

Features

Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.2 is a compatibility release with no new features.

Product Snapshot

Note: Tanzu Kubernetes Grid Integrated Edition Management Console provides an opinionated installation of TKGI. The supported versions may differ from or be more limited than what is generally supported by TKGI.

Element Details
Version v1.8.2
Release date October 01, 2020
Installed Tanzu Kubernetes Grid Integrated Edition version v1.8.2
Installed Ops Manager version v2.10.1
Installed Kubernetes version v1.17.11+vmware.1
Compatible NSX-T versions v3.0, v2.5.1, v2.5.0
Installed Harbor Registry version v1.10.3
Windows stemcells vSphere v7.0: v2019.15
vSphere v6.7 or v6.5: v2019.15 and later

Upgrade Path

The supported upgrade path to Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.2 is from Tanzu Kubernetes Grid Integrated Edition v1.7.0 and later.

Known Issues

The Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.2 has the same known issues as v1.8.0.

TKGI Management Console 1.8.1

Release Date: July 23, 2020

Features

Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.1 is a compatibility release with no new features.

Product Snapshot

Note: Tanzu Kubernetes Grid Integrated Edition Management Console provides an opinionated installation of TKGI. The supported versions may differ from or be more limited than what is generally supported by TKGI.

Element Details
Version v1.8.1
Release date July 23, 2020
Installed Tanzu Kubernetes Grid Integrated Edition version v1.8.1
Installed Ops Manager version v2.9.6
Installed Kubernetes version v1.17.8+vmware.1
Compatible NSX-T versions v3.0, v2.5.1, v2.5.0
Installed Harbor Registry version v1.10.3
Windows stemcells vSphere v7.0: v2019.15
vSphere v6.7 or v6.5: v2019.15 and later

Upgrade Path

The supported upgrade path to Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.1 is from Tanzu Kubernetes Grid Integrated Edition v1.7.0 and later.

Known Issues

The Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.1 has the same known issues as v1.8.0.

TKGI Management Console 1.8.0

Release Date: June 30, 2020

Features

Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.0 updates include:

  • Support for vSphere 7
  • Support for NSX-T 3.0
  • Rebranding to Tanzu Kubernetes Grid Integrated Edition Management Console
  • Specify FQDN for the Ops Manager VM during upgrade

Product Snapshot

Note: Tanzu Kubernetes Grid Integrated Edition Management Console provides an opinionated installation of TKGI. The supported versions may differ from or be more limited than what is generally supported by TKGI.

Element Details
Version v1.8.0
Release date June 30, 2020
Installed Tanzu Kubernetes Grid Integrated Edition version v1.8.0
Installed Ops Manager version v2.9.0
Installed Kubernetes version v1.17.5
Compatible NSX-T versions v3.0, v2.5.1, v2.5.0
Installed Harbor Registry version v1.10.3
Windows stemcells vSphere v7.0: v2019.15
vSphere v6.7 or v6.5: v2019.15 and later

Upgrade Path

The supported upgrade path to Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.0 is from Tanzu Kubernetes Grid Integrated Edition v1.7.0 and later.

Note: VMware recommends upgrading to TKGI Management Console v1.8.1 or later, not upgrading to v1.8.0.

Known Issues

The Tanzu Kubernetes Grid Integrated Edition Management Console v1.8.0 has the following known issues:

vRealize Log Insight Integration Does Not Support HTTPS Connections

Symptom

The Tanzu Kubernetes Grid Integrated Edition Management Console integration to vRealize Log Insight does not support connections to the HTTPS port on the vRealize Log Insight server.

Workaround

  1. Use SSH to log in to the Tanzu Kubernetes Grid Integrated Edition Management Console appliance VM.
  2. Open the file /lib/systemd/system/pks-loginsight.service in a text editor.
  3. Add -e LOG_SERVER_ENABLE_SSL_VERIFY=false.
  4. Set -e LOG_SERVER_USE_SSL=true.

    The resulting file should look like the following example:

    ExecStart=/bin/docker run --privileged --restart=always --network=pks 
    -v /var/log/journal:/var/log/journal 
    --name=pks-loginsight 
    -e TYPE=gear2-vm 
    -e LOG_SERVER_HOST=${LOGINSIGHT_HOST} 
    -e LOG_SERVER_PORT=${LOGINSIGHT_PORT} 
    -e LOG_SERVER_ENABLE_SSL_VERIFY=false 
    -e LOG_SERVER_USE_SSL=true 
    -e LOG_SERVER_AGENT_ID=${LOGINSIGHT_ID} 
    pksoctopus/vrli-journald:v07092019
    
  5. Save the file and run systemctl daemon-reload.

  6. To restart the vRealize Log Insight service, run systemctl restart pks-loginsight.service.

Tanzu Kubernetes Grid Integrated Edition Management Console can now send logs to the HTTPS port on the vRealize Log Insight server.

vSphere HA causes Management Console ovfenv Data Corruption

Symptom

If you enable vSphere HA on a cluster, if the TKGI Management Console appliance VM is running on a host in that cluster, and if the host reboots, vSphere HA recreates a new TKGI Management Console appliance VM on another host in the cluster. Due to an issue with vSphere HA, the ovfenv data for the newly created appliance VM is corrupted and the new appliance VM does not boot up with the correct network configuration.

Workaround

  • In the vSphere Client, right-click the appliance VM and select Power > Shut Down Guest OS.
  • Right-click the appliance again and select Edit Settings.
  • Select VM Options and click OK.
  • Verify under Recent Tasks that a Reconfigure virtual machine task has run on the appliance VM.
  • Power on the appliance VM.

Base64 encoded file arguments are not decoded in Kubernetes profiles

Symptom

Some file arguments in Kubernetes profiles are base64 encoded. When the management console displays the Kubernetes profile, some file arguments are not decoded.

Workaround

Run echo "$content" | base64 --decode

Network profiles not immediately selectable

Symptom

If you create network profiles and then try to apply them in the Create Cluster page, the new profiles are not available for selection.

Workaround

Log out of the management console and log back in again.

Real-Time IP information not displayed for network profiles

Symptom

In the cluster summary page, only default IP pool, pod IP block, node IP block values are displayed, rather than the real-time values from the associated network profile.

Workaround

None


Please send any feedback you have to pks-feedback@pivotal.io.