TMC and TCE Compatibility in TCE v0.11.0

[joshrosso]

For the TCE v0.11.0 release, management-clusters must be able to be registered to TMC. At this time, VMware is only positioned to support registration with TKG clusters. This is due to current limitations in testing, resourcing, and pursuit to create stable libraries in tanzu-framework.

With the above, TCE will bind its next release to TKG 1.5.1. This means TCE will ship management and workload clusters that are like-for-like with TKG 1.5.1, with the following exceptions:

• TCE will ship a different flavor of antrea; it will have some enterprise features removed.
• TCE will ship its user-managed package repository; The TKG standard repository will not be present.

In summary, with the 2 exceptions above, TCE clusters will be the same as TKG clusters. The goal is that TMC does not need to treat TCE clusters different from TKG clusters.

The 2 primary units of work are:

1. Roll TCE back to framework version v0.11.1; which puts us in sync with TKG 1.5.1 from a client perspective.
2. Create a valid TKG/TKR BOM and compatibility files based on v1.5.1 (projects.registry.vmware.com/tkg/tkg-bom:v1.5.1)
   1. valid is defined as using the correct flavor of antrea

Issue Tracking

• Revert Framework version to v0.11.1 #3275
  • Revert back to TF 0.11.1 #3283
• Create a community-edition release based on the TKG 1.5.1 BoM #3286
• Setup binary signing based on new binary build/directory structure #3320
• TKG client library makes assumption about standard-package-repo existence when doing upgrades, breaking TCE cluster upgrades tanzu-framework#1749

[joshrosso]

Adding all of TCE engineering to this issue.

Once the code-level work is done, we all need to be able to go in and validate this.

[joshrosso]

We've validated on our side that registration of management clusters works and LCM is possible.

See #3498 for details.