It is recommended to install Calico using the primary installation method #11200
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
What would you like to be added
Please take a look at the reply for this calico's issue: projectcalico/calico#6412 (comment)
Why is this needed
The current method of installing Calico does not install the API server for provides a REST API for Calico. Moreover, the APIs used by Calico’s features are all tested and verified using
projectcalico.org/v3
. Most importantly, most Calico users are unaware of this point to note.Therefore, it is hoped that Kubespray can support enabling kubectl to manage Calico APIs.
The text was updated successfully, but these errors were encountered: