- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 156 for Fields (0.23 sec)
-
manifests/charts/UPDATING-CHARTS.md
due to design choices in Helm. The underlying Kubernetes resources we configure have 1000s of fields; given enough users and bespoke use cases, eventually someone will want to customize every one of those fields. If all fields are exposed in `values.yaml`, we end up with an massive API that is also likely worse than just using the Kubernetes API directly.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jul 27 18:28:55 GMT 2023 - 3.2K bytes - Viewed (0) -
common-protos/k8s.io/api/certificates/v1beta1/generated.proto
// honor this field as long as the requested duration is not greater than the // maximum duration they will honor per the --cluster-signing-duration CLI // flag to the Kubernetes controller manager. // // Certificate signers may not honor this field for various reasons: // // 1. Old signer that is unaware of the field (such as the in-tree // implementations prior to v1.22)
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 6.7K bytes - Viewed (0) -
common-protos/k8s.io/api/storage/v1alpha1/generated.proto
// inlineVolumeSpec contains all the information necessary to attach // a persistent volume defined by a pod's inline VolumeSource. This field // is populated only for the CSIMigration feature. It contains // translated fields from a pod's inline VolumeSource to a // PersistentVolumeSpec. This field is alpha-level and is only // honored by servers that enabled the CSIMigration feature. // +optional
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 9.4K bytes - Viewed (0) -
common-protos/k8s.io/api/resource/v1alpha2/generated.proto
repeated ResourceClaimTemplate items = 2; } // ResourceClaimTemplateSpec contains the metadata and fields for a ResourceClaim. message ResourceClaimTemplateSpec { // ObjectMeta may contain labels and annotations that will be copied into the PVC // when creating it. No other fields are allowed and will be rejected during // validation. // +optional
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) -
licenses/cloud.google.com/go/trace/LICENSE
END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Nov 01 23:31:22 GMT 2022 - 11.1K bytes - Viewed (0) -
licenses/github.com/AdaLogics/go-fuzz-headers/LICENSE
END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Jun 28 18:00:28 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/longrunning/LICENSE
END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Nov 01 23:31:22 GMT 2022 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/auth/LICENSE
END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 30 13:56:46 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/btree/LICENSE
END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/gnostic-models/LICENSE
END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Jul 24 18:16:35 GMT 2023 - 11.1K bytes - Viewed (0)