Get desktop application:
View/edit binary Protocol Buffers messages
BoundedInteger to capture the range of max or min for a particular constraint.
Used in:
Used in:
self_signed will generate local certificates on the node.
Additional options will be for loading pregenerated certs. Also support for CSR and generation workflow.
Config is the k8s pod specific configuration for a node.
Used in:
Command to pass into pod.
Command args to pass into the pod.
Docker image to use with pod.
Map of environment variables to pass into the pod.
Specific entry point command for accessing the pod.
Mount point for configuration inside the pod.
Default configuration file name for the pod.
Sleeptime before starting the pod.
Certificate configuration
Byte data for the startup configuration file.
File is always relative to the topology configuration file.
Docker image to use as an init container for the pod.
Vendor-specific data
HostConstraint is a constraint on the host where the node is running.
Used in:
Includes the required kernel parameters that need to be configured.
Interface keys must be the same as the links a,z int.
Used in:
Name of the interface provided by Node implementation. This will be used to map the int_name into a vendor specific interface name. Vendor operators should provide the name mapping from the node interface key to this vendor specific name.
Internal device name. This name matches the key in the Node interface map. It will be returned by the operator. Assigned by KNE.
Desired MTU for the interface.
Peer node name. Assigned by KNE.
Peer interface name. Assigned by KNE.
Uid is the internal link identifier used by Meshnet.
Name of group to which this interface belongs
Type of the interface - Loopback, Management , Data etc.
ip_address associated with the interface.
Used in:
KernelParam is a parameter on the host kernel.
Used in:
MIB style name of the kernel state to constrain.
Link is single link between nodes in the topology. Interfaces must start eth1 - eth0 is the default k8s interface.
Used in:
Node is a single container inside the topology
Used in:
Name of the node in the topology. Must be unique.
Metadata labels describing the node.
Pod specific configuration of the node.
Map of services to enable on the node. The key is the external load balancer port to be used by the service. Multiple external services can be mapped to a single internal service port by reusing the inside_port in the service definition.
Any k8s constraints required by node.
Vendor enum replaces type.
Model of the node.
Version string used to identify a software release.
Operating system type.
Interfaces is a map of container interfaces used by the node. If interfaces is empty the interfaces defined in the links portion of the topology will be populated into the node.
Any host constraints required by the node. These may not be required by a vendor, but it can be used to provide requirements for the node.
Assigned by KNE. Cluster-internal IP assigned by Kubernetes for the pod. This IP comes from the worker node's IP pool.
Used in:
Used in:
Certificate name on the node.
Key name on the node.
RSA keysize to use for key generation.
Common name to set in the cert.
Service is k8s Service to exposed to the cluster. The initial input can be provided by the user for which services they would like exposed. Once the service is created KNE will fill in the outside information for the user to access the services. The user should specify inside port for this is the port the container will listen on.
Used in:
Name of the service (optional)
Inside port to map Node (container listening port)
Assigned by KNE.
Outside port used by service. (same a service key)
External IP assigned by cluster load balancer.
Used internally by KNE.
Cluster IP for the service.
Port on the K8s worker node used by the cluster.
List of service names to be mapped to the port (optional). If only one field out of "name" or "names" is provided in the input topo, the unspecified field is ignored. If both are provided, names in both fields are considered excluding any duplicate values.
Topology message defines what nodes and links will be created inside the mesh.
Used in:
, ,Name of the topology - will be linked to the cluster name
List of nodes in the topology
connections between Nodes.
Vendor of the node. Topology manager uses this enum to dispatch the node to the correct controller.
Used in:
,