metalctl network
manage network entities
Synopsis
networks can be attached to a machine or firewall such that they can communicate with each other.
Options
-h, --help help for network
Options inherited from parent commands
--api-token string api token to authenticate. Can be specified with METALCTL_API_TOKEN environment variable.
--api-url string api server address. Can be specified with METALCTL_API_URL environment variable.
-c, --config string alternative config file path, (default is ~/.metalctl/config.yaml).
Example config.yaml:
---
apitoken: "alongtoken"
...
--debug debug output
--force-color force colored output even without tty
--kubeconfig string Path to the kube-config to use for authentication and authorization. Is updated by login. Uses default path if not specified.
--no-headers do not print headers of table output format (default print headers)
-o, --output-format string output format (table|wide|markdown|json|yaml|template), wide is a table with more columns. (default "table")
--template string output template for template output-format, go template format.
For property names inspect the output of -o json or -o yaml for reference.
Example for machines:
metalctl machine list -o template --template "{{ .id }}:{{ .size.id }}"
--yes-i-really-mean-it skips security prompts (which can be dangerous to set blindly because actions can lead to data loss or additional costs)
SEE ALSO
- metalctl - a cli to manage entities in the metal-stack api
- metalctl network allocate - allocate a network
- metalctl network apply - applies one or more networks from a given file
- metalctl network create - creates the network
- metalctl network delete - deletes the network
- metalctl network describe - describes the network
- metalctl network edit - edit the network through an editor and update
- metalctl network free - free a network
- metalctl network ip - manage ip entities
- metalctl network list - list all networks
- metalctl network update - updates the network