- Sort Score
- Result 10 results
- Languages All
Results 11 - 13 of 13 for vagrant (0.1 sec)
-
architecture/networking/controllers.md
`kube.Client` just bundles these all in one place, so we have a single object to pass around anywhere we need Kubernetes access. Additionally, it has a fake client variant, that does the same thing but with fake clients for use in unit tests. Aside from this, there are a few conveniences and workarounds built-in to the client to make things simpler.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Fri Feb 09 17:41:25 UTC 2024 - 4.9K bytes - Viewed (0) -
common-protos/k8s.io/api/authorization/v1beta1/generated.proto
repeated string items = 1; } // LocalSubjectAccessReview checks whether or not a user or group can perform an action in a given namespace. // Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions // checking. message LocalSubjectAccessReview { // Standard list metadata.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 11.9K bytes - Viewed (0) -
tools/istio-iptables/pkg/README.md
So basically selecting the right binary for one of the above cases is a heuristic with 2 inputs: 1. Does the particular binary variant (legacy, nft, ip6tables) even exist in $PATH? 1. In the current netns context, are there already rules defined in one of (legacy, nft) tables? If so, prefer that one.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Mar 11 17:46:23 UTC 2024 - 3.7K bytes - Viewed (0)