Skip to content

Latest commit

 

History

History
87 lines (69 loc) · 5.35 KB

galaxy-config.md

File metadata and controls

87 lines (69 loc) · 5.35 KB
Raw

Galaxy Configuration

Default network and Supported networks

You may edit galaxy-etc ConfigMap in galaxy.yaml to update DefaultNetworks and NetworkConf for all supported networks.

Galaxy support multiple default networks and configures them to pods according to the order of the networks of DefaultNetworks.

{
  "NetworkConf":[
    {"name":"tke-route-eni", "type":"tke-route-eni", "eni":"eth1", "routeTable":1},
    {"name":"galaxy-flannel", "type":"galaxy-flannel", "delegate":{"type":"galaxy-veth"}, "subnetFile":"/run/flannel
/subnet.env"},
    {"name":"galaxy-k8s-vlan", "type":"galaxy-k8s-vlan", "device":"eth1", "default_bridge_name": "br0"},
    {"name": "galaxy-k8s-sriov", "type": "galaxy-k8s-sriov", "device": "eth1", "vf_num": 10},
    {"name":"galaxy-underlay-veth", "type":"galaxy-underlay-veth", "device":"eth1"}
  ],
  "DefaultNetworks": ["galaxy-flannel"],
  "ENIIPNetwork": "galaxy-k8s-vlan"
}

If a network name is empty, Galaxy assumes its name equals its type name. Network name is used when a pod asks for a specific network.

Galaxy assumes the default network for pods who want eni ip and has no k8s.v1.cni.cncf.io/networks annotation is the value of ENIIPNetwork regardless of DefaultNetworks. Adding ENIIPNetwork is to avoid of adding k8s.v1.cni.cncf.io/networks annotation for every pod which wants underlay networks.

Co-work with other cni plugins

Galaxy works well and peacefully with other cni plugins by loading unknown network configurations which are absent from galaxy-etc ConfigMap from --network-conf-dir(default /etc/cni/net.d/) . These configurations will be loaded each time when setting up networks for a pod.

But please be careful not to add a configuration file with alphabetical order higher than the Galaxy CNI configuration file 00-galaxy.conf, otherwise Kubelet will call your CNI plugin first than Galaxy CNI plugin.

Configure specific networks for a pod

Galaxy supports to configure specific and multiple networks for a single pod. It matches a pod's k8s.v1.cni.cncf.io /networks annotation value with the name of networks, so you can configure different cni implementations of the same network name.

Pod Annotation Usage Expain
k8s.v1.cni.cncf.io/networks k8s.v1.cni.cncf.io/networks: galaxy-flannel,galaxy-k8s-sriov Galaxy setup specified networks according to the order of its values if not empty for a pod, otherwise make use of DefaultNetworks to do that.

Galaxy command line args

Usage of galaxy:
      --alsologtostderr                   log to standard error as well as files
      --bridge-nf-call-iptables           Ensure bridge-nf-call-iptables is set/unset (default true)
      --cni-paths stringSlice             additional cni paths apart from those received from kubelet (default [/opt/cni/galaxy/bin])
      --flannel-allocated-ip-dir string   IP storage directory of flannel cni plugin (default "/var/lib/cni/networks")
      --flannel-gc-interval duration      Interval of executing flannel network gc (default 10s)
      --gc-dirs string                    Comma separated configure storage directory of cni plugin, the file names in this directory are container ids (default "/var/lib/cni/flannel,/var/lib/cni/galaxy,/var/lib/cni/galaxy/port")
      --hostname-override string          kubelet hostname override, if set, galaxy use this as node name to get node from apiserver
      --ip-forward                        Ensure ip-forward is set/unset (default true)
      --json-config-path string           The json config file location of galaxy (default "/etc/galaxy/galaxy.json")
      --kubeconfig string                 The kube config file location of APISwitch, used to support TLS
      --log-backtrace-at traceLocation    when logging hits line file:N, emit a stack trace (default :0)
      --log-dir string                    If non-empty, write log files in this directory
      --log-flush-frequency duration      Maximum number of seconds between log flushes (default 5s)
      --logtostderr                       log to standard error instead of files (default true)
      --master string                     The address and port of the Kubernetes API server
      --network-conf-dir string           Directory to additional network configs apart from those in json config (default "/etc/cni/net.d/")
      --network-policy                    Enable network policy function
      --route-eni                         Ensure route-eni is set/unset
      --stderrthreshold severity          logs at or above this threshold go to stderr (default 2)
  -v, --v Level                           log level for V logs
      --version version[=true]            Print version information and quit
      --vmodule moduleSpec                comma-separated list of pattern=N settings for file-filtered logging

How Galaxy works

How Galaxy works

This is how Galaxy supports running flannel network.

  1. Flannel on each Kubelet allocates a subnet and saves it on etcd and local disk (/run/flannel/subnet.env)
  2. Kubelet launches SDN CNI process according to CNI configuration.
  3. SDN CNI process calls Galaxy via unix socket with all args from Kubelet.
  4. Galaxy calls Flannel CNI to parse subnet infos from /run/flannel/subnet.env.
  5. Flannel CNI calls either Bridge CNI or Veth CNI to configure networks for PODs.