- Sort Score
- Result 10 results
- Languages All
Results 211 - 220 of 399 for appropriately (0.11 sec)
-
licenses/k8s.io/kube-openapi/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/kube-openapi/pkg/validation/spec/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Dec 16 22:26:43 UTC 2020 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/kustomize/api/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Apr 22 22:59:25 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/mcs-api/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Mar 12 21:17:55 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/structured-merge-diff/v4/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sun Aug 30 14:15:49 UTC 2020 - 11.1K bytes - Viewed (0) -
licenses/github.com/docker/distribution/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/github.com/go-logr/stdr/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/github.com/go-openapi/jsonreference/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/btree/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
helm-releases/minio-3.5.6.tgz
.Capabilities.KubeVersion.Version -}} {{- print "networking.k8s.io/v1" -}} {{- end -}} {{- end -}} {{/* Return the appropriate apiVersion for deployment. */}} {{- define "minio.deployment.apiVersion" -}} {{- if semverCompare "<1.9-0" .Capabilities.KubeVersion.Version -}} {{- print "apps/v1beta2" -}} {{- else -}} {{- print "apps/v1" -}} {{- end -}} {{- end -}} {{/* Return the appropriate apiVersion for statefulset. */}} {{- define "minio.statefulset.apiVersion" -}} {{- if semverCompare "<1.16-0" .C...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Feb 19 20:34:14 UTC 2022 - 17.6K bytes - Viewed (0)