- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 158 for We (0.18 sec)
-
cni/pkg/repair/repaircontroller.go
// once the pod restarts (in CrashLoopBackoff), which can take some time. // We don't want to constantly try to apply the iptables rules, which is unneeded and will fail. // Instead, we track which UIDs we repaired and skip them if already repaired. // // An alternative would be to write something to the Pod (status, annotation, etc). // However, this requires elevated privileges we want to avoid if uid, f := c.repairedPods[key]; f {
Go - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Feb 10 00:31:55 GMT 2024 - 10.4K bytes - Viewed (0) -
istioctl/pkg/tag/tag.go
} if err := analyzeWebhook(resName, istioNS, tagWhYAML, revision, kubeClient.RESTConfig()); err != nil { // if we have a conflict, we will fail. If --skip-confirmation is set, we will continue with a // warning; when actually applying we will also confirm to ensure the user does not see the // warning *after* it has applied if !skipConfirmation { _, _ = stderr.Write([]byte(err.Error()))
Go - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 08:32:06 GMT 2024 - 16.3K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/values.yaml
# # The PSP controller would add corresponding annotations to the pod spec for each container. However, this happens before # the inject adds additional containers, so we must specify them explicitly here. With the above example, we could specify: # injectedAnnotations: # container.apparmor.security.beta.kubernetes.io/istio-init: runtime/default
Others - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 16:58:23 GMT 2024 - 19.6K bytes - Viewed (0) -
licenses/cloud.google.com/go/trace/LICENSE
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 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
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Mon Jun 28 18:00:28 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/containerd/stargz-snapshotter/estargz/LICENSE
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Fri Jul 30 04:02:55 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/longrunning/LICENSE
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Nov 01 23:31:22 GMT 2022 - 11.1K bytes - Viewed (0) -
licenses/github.com/docker/distribution/LICENSE
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp/LICENSE
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Jul 26 01:07:39 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/github.com/prometheus/prometheus/LICENSE
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 identification within third-party archives.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Jul 14 16:53:19 GMT 2021 - 11.1K bytes - Viewed (0)