Skip to main content
Calico Open Source 3.32 (latest) documentation

Enable kubectl to manage Calico APIs

deprecation notice

The aggregated API server (calico-apiserver) is deprecated and will be removed in a future release. For new installations, use native v3 CRDs. For existing clusters, see Migrate from API server to native CRDs.

Big picture​

Install the Calico API server on an existing cluster to enable management of Calico APIs using kubectl.

tip

You can use native v3 CRDs to manage projectcalico.org/v3 resources directly with kubectl without installing the aggregation API server. If you are setting up a new cluster and want a simpler architecture, consider native v3 CRDs instead.

Value​

The API server provides a REST API for Calico, and allows management of projectcalico.org/v3 APIs using kubectl without the need for calicoctl.

note

New operator-based installations of Calico include the API server component by default, so the instructions in this document are not required.

Before you begin​

  • Make sure you have a cluster with Calico installed using the Kubernetes API data store. If not, you can migrate from etcd.

  • Upgrade to Calico v3.20+ using the appropriate upgrade instructions.

  • For non-operator installations, you will need a machine with openssl installed.

Concepts​

calicoctl vs kubectl​

In previous releases, calicoctl has been required to manage Calico API resources in the projectcalico.org/v3 API group. The calicoctl CLI tool provides important validation and defaulting on these APIs. The Calico API server performs that defaulting and validation server-side, exposing the same API semantics without a dependency on calicoctl.

Alternatively, when using native v3 CRDs, projectcalico.org/v3 resources are native CRDs, so kubectl works directly without needing either the API server or calicoctl for resource management.

calicoctl is still required for the following subcommands:

How to​

Install the API server​

Select the method below based on your installation method.

  1. Create an instance of an operator.tigera.io/APIServer with the following command.

    kubectl create -f - <<EOF
    apiVersion: operator.tigera.io/v1
    kind: APIServer
    metadata:
      name: default
    spec: {}
    EOF

  2. Confirm it appears as Available with the following command.

    kubectl get tigerastatus apiserver

    You should see the following output:

    NAME        AVAILABLE   PROGRESSING   DEGRADED   SINCE
    apiserver   True        False         False      1m10s

After following the above steps, you should see the API server pod become ready, and Calico API resources become available. You can check whether the APIs are available with the following command:

kubectl api-resources | grep '\sprojectcalico.org'

You should see the following output:

bgpconfigurations                 bgpconfig,bgpconfigs                            projectcalico.org              false        BGPConfiguration
bgppeers                                                                          projectcalico.org              false        BGPPeer
clusterinformations               clusterinfo                                     projectcalico.org              false        ClusterInformation
felixconfigurations               felixconfig,felixconfigs                        projectcalico.org              false        FelixConfiguration
globalnetworkpolicies             gnp,cgnp,calicoglobalnetworkpolicies            projectcalico.org              false        GlobalNetworkPolicy
globalnetworksets                                                                 projectcalico.org              false        GlobalNetworkSet
hostendpoints                     hep,heps                                        projectcalico.org              false        HostEndpoint
ippools                                                                           projectcalico.org              false        IPPool
kubecontrollersconfigurations                                                     projectcalico.org              false        KubeControllersConfiguration
networkpolicies                   cnp,caliconetworkpolicy,caliconetworkpolicies   projectcalico.org              true         NetworkPolicy
networksets                       netsets                                         projectcalico.org              true         NetworkSet
profiles                                                                          projectcalico.org              false        Profile
note

kubectl may continue to prefer the crd.projectcalico.org API group due to the way it caches APIs locally. You can force kubectl to update by removing its cache directory for your cluster. By default, the cache is located in $(HOME)/.kube/cache.

Use kubectl for projectcalico.org APIs​

Once the API server has been installed, you can use kubectl to interact with the Calico APIs. For example, you can view and edit IP pools.

kubectl get ippools

You should see output that looks like this:

NAME                  CREATED AT
default-ipv4-ippool   2021-03-19T16:47:12Z

Uninstall the Calico API server​

To uninstall the API server, use the following instructions depending on your install method.

   kubectl delete apiserver default

Once removed, you will need to use calicoctl to manage projectcalico.org/v3 APIs, unless you are using native v3 CRDs where kubectl works directly.

Next steps​

Recommended tutorials