package protos

Get desktop application:
View/edit binary Protocol Buffers messages

CNIClient is the API between cni-plugin and enforcerd

• rpc CNIContainerEvent (CNIContainerEventRequest, ContainerEventResponse)

  monitor.proto:24

  ContainerEvent will be invoked by the CNI plugin on the following events at this point: - ‘cmdADD start’ - 'cmdDEL delete'

  message CNIContainerEventRequest

  monitor.proto:31

  • CNIContainerEventRequest.Type type = 1

  • string containerID = 2

  • string netnsPath = 3

  • string podName = 4

  • string podNamespace = 5

RunCClient is the API between runc-proxy and enforcerd

• rpc RunCContainerEvent (RunCContainerEventRequest, ContainerEventResponse)

  monitor.proto:16

  ContainerEvent will be invoked by the runc proxy on the following events at this point: - ‘runc start’ - 'runc delete'

  message RunCContainerEventRequest

  monitor.proto:27

  • repeated string commandLine = 1

    the full commandline of the runc command incl. flags, etc. - this is expected to come from `os.Args`

• rpc RuncProxyStarted (google.protobuf.Empty, google.protobuf.Empty)

  monitor.proto:10

  RuncProxyStarted is called by the PCC agent once the runc proxy has been started

Used in: CNIContainerEventRequest

• ADD = 0

• DELETE = 1

Used as response type in: CNI.CNIContainerEvent, RunC.RunCContainerEvent

• string errorMessage = 1

  errorMessage will be empty on success, and have an error message set only on an error