pub struct InspectPodInfraConfig {Show 18 fields
pub dns_option: Option<Vec<String>>,
pub dns_search: Option<Vec<String>>,
pub dns_server: Option<Vec<String>>,
pub host_add: Option<Vec<String>>,
pub host_network: Option<bool>,
pub network_options: Option<HashMap<String, Vec<String>>>,
pub networks: Option<Vec<String>>,
pub no_manage_hosts: Option<bool>,
pub no_manage_resolv_conf: Option<bool>,
pub port_bindings: Option<HashMap<String, Option<Vec<InspectHostPort>>>>,
pub static_ip: Option<String>,
pub static_mac: Option<String>,
pub cpu_period: Option<u64>,
pub cpu_quota: Option<i64>,
pub cpuset_cpus: Option<String>,
pub pid_ns: Option<String>,
pub userns: Option<String>,
pub uts_ns: Option<String>,
}
Expand description
InspectPodInfraConfig contains the configuration of the pod’s infra container.
Fields§
§dns_option: Option<Vec<String>>
DNSOption is a set of DNS options that will be used by the infra container’s resolv.conf and shared with the remainder of the pod.
dns_search: Option<Vec<String>>
DNSSearch is a set of DNS search domains that will be used by the infra container’s resolv.conf and shared with the remainder of the pod.
dns_server: Option<Vec<String>>
DNSServer is a set of DNS Servers that will be used by the infra container’s resolv.conf and shared with the remainder of the pod.
host_add: Option<Vec<String>>
HostAdd adds a number of hosts to the infra container’s resolv.conf which will be shared with the rest of the pod.
host_network: Option<bool>
HostNetwork is whether the infra container (and thus the whole pod) will use the host’s network and not create a network namespace.
network_options: Option<HashMap<String, Vec<String>>>
NetworkOptions are additional options for each network
networks: Option<Vec<String>>
Networks is a list of CNI networks the pod will join.
no_manage_hosts: Option<bool>
NoManageHosts indicates that the pod will not manage /etc/hosts and instead each container will handle their own.
no_manage_resolv_conf: Option<bool>
NoManageResolvConf indicates that the pod will not manage resolv.conf and instead each container will handle their own.
port_bindings: Option<HashMap<String, Option<Vec<InspectHostPort>>>>
PortBindings are ports that will be forwarded to the infra container and then shared with the pod.
static_ip: Option<String>
StaticIP is a static IPv4 that will be assigned to the infra container and then used by the pod.
static_mac: Option<String>
StaticMAC is a static MAC address that will be assigned to the infra container and then used by the pod.
cpu_period: Option<u64>
CPUPeriod contains the CPU period of the pod
cpu_quota: Option<i64>
CPUQuota contains the CPU quota of the pod
cpuset_cpus: Option<String>
CPUSetCPUs contains linux specific CPU data for the container
pid_ns: Option<String>
Pid is the PID namespace mode of the pod’s infra container
userns: Option<String>
UserNS is the usernamespace that all the containers in the pod will join.
uts_ns: Option<String>
UtsNS is the uts namespace that all containers in the pod will join
Trait Implementations§
Source§impl Clone for InspectPodInfraConfig
impl Clone for InspectPodInfraConfig
Source§fn clone(&self) -> InspectPodInfraConfig
fn clone(&self) -> InspectPodInfraConfig
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more