- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for processing (0.25 sec)
-
common-protos/k8s.io/api/resource/v1alpha2/generated.proto
// for cluster-scoped resources and non-empty for namespaced // resources. // +optional optional string namespace = 4; } // ResourceHandle holds opaque resource data for processing by a specific kubelet plugin. message ResourceHandle { // DriverName specifies the name of the resource driver whose kubelet // plugin should be invoked to process this ResourceHandle's data once it
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 14.4K bytes - Viewed (0) -
cni/README.md
1. By installing a separate, very basic "CNI plugin" binary onto the node to forward low-level pod lifecycle events (CmdAdd/CmdDel/etc) from whatever node-level CNI subsystem is in use to this node agent for processing via socket. 1. By running as a node-level daemonset that: - listens for these UDS events from the CNI plugin (which fire when new pods are spawned in an ambient-enabled namespace), and adds those pods to the ambient mesh.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0) -
common-protos/k8s.io/api/batch/v1/generated.proto
// +optional // +patchMergeKey=type // +patchStrategy=merge // +listType=atomic repeated JobCondition conditions = 1; // Represents time when the job controller started processing a job. When a // Job is created in the suspended state, this field is not set until the // first time it is resumed. This field is reset every time a Job is resumed
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 21.1K bytes - Viewed (0) -
architecture/networking/pilot.md
#### Mesh Config Mesh Config controller is a pretty simple controller, reading from `ConfigMap`(s) (multiple if `SHARED_MESH_CONFIG` is used), processing and merging these into a the typed `MeshConfig`. It then exposes this over a simple `mesh.Watcher`, which just exposes a way to access the current `MeshConfig` and get notified when it changes. #### Ingress
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 19.1K bytes - Viewed (0) -
common-protos/k8s.io/api/storage/v1beta1/generated.proto
// method), and that the Kubernetes attach detach controller should call // the attach volume interface which checks the volumeattachment status // and waits until the volume is attached before proceeding to mounting. // The CSI external-attacher coordinates with CSI volume driver and updates // the volumeattachment status when the attach operation is complete.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 24.9K bytes - Viewed (0) -
cni/pkg/install/cniconfig.go
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jan 26 20:34:28 GMT 2024 - 10.4K bytes - Viewed (0) -
common-protos/k8s.io/api/storage/v1/generated.proto
// method), and that the Kubernetes attach detach controller should call // the attach volume interface which checks the volumeattachment status // and waits until the volume is attached before proceeding to mounting. // The CSI external-attacher coordinates with CSI volume driver and updates // the volumeattachment status when the attach operation is complete.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 24.7K bytes - Viewed (0) -
cni/pkg/nodeagent/podcgroupns.go
// plus we want to return whatever we can to the user. res, err := p.processEntry(p.proc, netnsObserved, desiredUIDs, entry) if err != nil { log.Debugf("error processing entry: %s %v", entry.Name(), err) continue } if res == nil { continue } pod := pods[res.uid] netns := &NetnsWithFd{ netns: res.netns, fd: res.netnsfd, inode: res.inode,
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Apr 12 21:47:31 GMT 2024 - 11K bytes - Viewed (0)