Closed jinsongo closed 3 years ago
@Fei-Guo @christopherhein @charleszheng44 @gyliu513
@wangjsty can you add this information to #41 ?
/close duplicate issue for tracking CRS.
@christopherhein: Closing this issue.
@christopherhein I would like to track the issue by the duplicated one #41. Thanks!
What steps did you take and what happened: [A clear and concise description on how to REPRODUCE the bug.]
Follow the proposal guides: https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/proposals/20200220-cluster-resource-set.md https://cluster-api.sigs.k8s.io/tasks/experimental-features/experimental-features.html?highlight=ClusterResourceSet#enabling-experimental-features-on-existing-management-clusters
The following problem appears, but the two apiservers are running normally by kubectl command.
What did you expect to happen: The secret and configmap are deployed in nested clusters
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): v1.21.1/etc/os-release
): Red Hat Enterprise Linux 8/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]