This sections describes the
calicoctl create command.
Read the calicoctl command line interface user reference for a full list of calicoctl commands.
Note: The available actions for a specific resource type may be limited based on the datastore used for Calico (etcdv3 / Kubernetes API). Please refer to the Resources section for details about each resource type.
Displaying the help text for ‘calicoctl create’ command
calicoctl create --help to display the following help menu for the
Usage: calicoctl create --filename=<FILENAME> [--recursive] [--skip-empty] [--skip-exists] [--config=<CONFIG>] [--namespace=<NS>] Examples: # Create a policy using the data in policy.yaml. calicoctl create -f ./policy.yaml # Create a policy based on the JSON passed into stdin. cat policy.json | calicoctl create -f - Options: -h --help Show this screen. -f --filename=<FILENAME> Filename to use to create the resource. If set to "-" loads from stdin. If filename is a directory, this command is invoked for each .json .yaml and .yml file within that directory, terminating after the first failure. -R --recursive Process the filename specified in -f or --filename recursively. --skip-empty Do not error if any files or directory specified using -f or --filename contain no data. --skip-exists Skip over and treat as successful any attempts to create an entry that already exists. -c --config=<CONFIG> Path to the file containing connection configuration in YAML or JSON format. [default: /etc/calico/calicoctl.cfg] -n --namespace=<NS> Namespace of the resource. Only applicable to NetworkPolicy, NetworkSet, and WorkloadEndpoint. Uses the default namespace if not specified. --context=<context> The name of the kubeconfig context to use. Description: The create command is used to create a set of resources by filename or stdin. JSON and YAML formats are accepted. Valid resource types are: * bgpConfiguration * bgpPeer * felixConfiguration * globalNetworkPolicy * hostEndpoint * ipPool * networkPolicy * networkSet * node * profile * workloadEndpoint Attempting to create a resource that already exists is treated as a terminating error unless the --skip-exists flag is set. If this flag is set, resources that already exist are skipped. The output of the command indicates how many resources were successfully created, and the error reason if an error occurred. If the --skip-exists flag is set then skipped resources are included in the success count. The resources are created in the order they are specified. In the event of a failure creating a specific resource it is possible to work out which resource failed based on the number of resources successfully created.
Create a set of resources (of mixed type) using the data in resources.yaml.
calicoctl create -f ./resources.yaml
Results indicate that 8 resources were successfully created.
Successfully created 8 resource(s)
Create the same set of resources reading from stdin.
cat resources.yaml | calicoctl create -f -
Results indicate failure because the first resource (in this case a Profile) already exists.
Failed to create any resources: resource already exists: Profile(name=profile1)
-f --filename=<FILENAME> Filename to use to create the resource. If set to "-" loads from stdin. --skip-exists Skip over and treat as successful any attempts to create an entry that already exists. -n --namespace=<NS> Namespace of the resource. Only applicable to NetworkPolicy and WorkloadEndpoint. Uses the default namespace if not specified.
-c --config=<CONFIG> Path to the file containing connection configuration in YAML or JSON format. [default: /etc/calico/calicoctl.cfg]