Bug description
Add tkg.tanzu.vmware.com/package-name label generically to all providers and secrets
Affected product area (please put an X in all that apply)
- ( ) APIs
- (x) Addons
- ( ) CLI
- ( ) Docs
- ( ) IAM
- ( ) Installation
- ( ) Plugin
- ( ) Security
- ( ) Test and Release
- ( ) User Experience
- ( ) Developer Experience
Expected behavior
when creating a workload cluster with custom cluster bootstrap, the workload cluster CP and worker nodes will be created but will never become Ready.
Steps to reproduce the bug
It appears that the AntreaConfig resources now need the tkg.tanzu.vmware.com/package-name label for the Add-on manager to install Antrea in the designated workload cluster.
labels:
tkg.tanzu.vmware.com/cluster-name: rito
tkg.tanzu.vmware.com/package-name: antrea.tanzu.vmware.com.1.7.2---vmware.1-tkg.1-advanced
Version (include the SHA if the version is not obvious)
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)
Bug description
Add tkg.tanzu.vmware.com/package-name label generically to all providers and secrets
Affected product area (please put an X in all that apply)
Expected behavior
when creating a workload cluster with custom cluster bootstrap, the workload cluster CP and worker nodes will be created but will never become Ready.
Steps to reproduce the bug
It appears that the
AntreaConfigresources now need thetkg.tanzu.vmware.com/package-name labelfor the Add-on manager to install Antrea in the designated workload cluster.labels:
tkg.tanzu.vmware.com/cluster-name: rito
tkg.tanzu.vmware.com/package-name: antrea.tanzu.vmware.com.1.7.2---vmware.1-tkg.1-advanced
Version (include the SHA if the version is not obvious)
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)