- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for filesystem (0.18 sec)
-
common-protos/k8s.io/api/core/v1/generated.proto
// fsType is the filesystem type of the volume that you want to mount. // Tip: Ensure that the filesystem type is supported by the host operating system. // Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. // More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore // TODO: how do we prevent errors in the filesystem from compromising the machine // +optional
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 255.8K bytes - Viewed (0) -
cni/README.md
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/storage/v1beta1/generated.proto
// mounted only with a single SELinux context. // // When "false", Kubernetes won't pass any special SELinux mount options to the driver. // This is typical for volumes that represent subdirectories of a bigger shared filesystem. // // Default is "false". // // +featureGate=SELinuxMountReadWriteOncePod // +optional optional bool seLinuxMount = 8; }
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) -
common-protos/k8s.io/api/storage/v1/generated.proto
// mounted only with a single SELinux context. // // When "false", Kubernetes won't pass any special SELinux mount options to the driver. // This is typical for volumes that represent subdirectories of a bigger shared filesystem. // // Default is "false". // // +featureGate=SELinuxMountReadWriteOncePod // +optional optional bool seLinuxMount = 8; }
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) -
architecture/networking/pilot.md
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) -
architecture/environments/operator.md
in-cluster CR is updated and the controller acts upon it to generate a new manifest to apply to the cluster. Note that both the charts and configuration profiles can come from three different sources: compiled-in, local filesystem. The source may be selected independently for the charts and profiles. The different steps in creating the manifest are as follows:
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Aug 09 22:09:18 GMT 2023 - 13.4K bytes - Viewed (0)