- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 51 for Namespace$2 (0.63 sec)
-
pkg/config/analysis/analyzers/testdata/injection-image-distroless.yaml
apiVersion: v1 kind: Namespace metadata: labels: istio-injection: enabled name: enabled-namespace --- # Namespace 'enabled-namespace-2' has istio injection enabled, so will be enforced. apiVersion: v1 kind: Namespace metadata: labels: istio-injection: enabled name: enabled-namespace-2 --- # Details-v1-pod-old is out of date and should get a warning. apiVersion: v1 kind: Pod metadata: labels:
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Nov 28 02:55:12 UTC 2023 - 1.4K bytes - Viewed (0) -
pkg/controller/util/selectors/bimultimap_test.go
putLabeledObject(key("pod-1", "namespace-2"), labels("a", "1")), putSelectingObject(key("hpa-1", "namespace-2"), selector("a", "1")), }, want: []expectation{ forwardSelect(key("hpa-1", "namespace-1")), // selects nothing forwardSelect(key("hpa-1", "namespace-2"), key("pod-1", "namespace-2")), reverseSelect(key("pod-1", "namespace-1")), // selects nothing
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Tue Dec 13 01:56:36 UTC 2022 - 16.9K bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/NOTES.txt
# Migration from istio-system Istio 1.0 includes the gateways in istio-system. Since the external IP is associated with the Service and bound to the namespace, it is recommended to: 1. Install the new gateway in a new namespace. 2. Copy any TLS certificate to the new namespace, and configure the domains. 3. Checking the new gateway work - for example by overriding the IP in /etc/hosts 4. Modify the DNS server to add the A record of the new namespace
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Apr 15 21:29:06 UTC 2020 - 1.5K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/NOTES.txt
# Migration from istio-system Istio 1.0 includes the gateways in istio-system. Since the external IP is associated with the Service and bound to the namespace, it is recommended to: 1. Install the new gateway in a new namespace. 2. Copy any TLS certificate to the new namespace, and configure the domains. 3. Checking the new gateway work - for example by overriding the IP in /etc/hosts 4. Modify the DNS server to add the A record of the new namespace
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Apr 15 21:29:06 UTC 2020 - 2K bytes - Viewed (0) -
pkg/zdsapi/zds.proto
enum Version { NOT_USED = 0; V1 = 1; } message ZdsHello { Version version = 1; } message WorkloadInfo { reserved "trust_domain"; // Deprecated reserved 4; string name = 1; string namespace = 2; string service_account = 3; } // Add a workload to the ztunnel. this will be accompanied by ancillary data contianing // the workload's netns file descriptor. message AddWorkload { string uid = 1;
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu May 23 22:07:03 UTC 2024 - 2.7K bytes - Viewed (0) -
pkg/workloadapi/security/authorization.proto
syntax = "proto3"; package istio.security; option go_package="pkg/workloadapi/security"; import "google/protobuf/empty.proto"; message Authorization { string name = 1; string namespace = 2; // Determine the scope of this RBAC policy. // If set to NAMESPACE, the 'namespace' field value will be used. Scope scope = 3; // The action to take if the request is matched with the rules.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Jun 21 20:45:12 UTC 2023 - 3K bytes - Viewed (0) -
pkg/workloadapi/workload.proto
message Service { // Name represents the name for the service. // For Kubernetes, this is the Service name. string name = 1; // Namespace represents the namespace for the service. string namespace = 2; // Hostname represents the FQDN of the service. // For Kubernetes, this would be <name>.<namespace>.svc.<cluster domain>. // TODO: support this field string hostname = 3;
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Jun 12 18:02:35 UTC 2024 - 12.9K bytes - Viewed (0) -
pilot/pkg/config/kube/gateway/testdata/route-binding.yaml.golden
kind: VirtualService metadata: annotations: internal.istio.io/parents: HTTPRoute/bind-cross-namespace.group-namespace1,HTTPRoute/bind-cross-namespace.group-namespace2 internal.istio.io/route-semantics: gateway creationTimestamp: null name: bind-cross-namespace-2-istio-autogenerated-k8s-gateway namespace: group-namespace1 spec: gateways: - istio-system/gateway-istio-autogenerated-k8s-gateway-slctr-labels hosts:
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Dec 11 20:21:53 UTC 2023 - 16.1K bytes - Viewed (0) -
pkg/apis/core/v1/helper/helpers.go
"k8s.io/apimachinery/pkg/selection" "k8s.io/apimachinery/pkg/util/validation" "k8s.io/kubernetes/pkg/apis/core/helper" ) // IsExtendedResourceName returns true if: // 1. the resource name is not in the default namespace; // 2. resource name does not have "requests." prefix, // to avoid confusion with the convention in quota // 3. it satisfies the rules in IsQualifiedName() after converted into quota resource name
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu May 30 23:03:54 UTC 2024 - 11.4K bytes - Viewed (0) -
tests/integration/telemetry/policy/helper_test.go
t.Helper() // Testing of Blackhole and Passthrough clusters: // Setup of environment: // 1. client and destination are deployed to app-1-XXXX namespace // 2. client is restricted to talk to destination via Sidecar scope where outbound policy is set (ALLOW_ANY, REGISTRY_ONLY) // and clients' egress can only be to service-2-XXXX/* and istio-system/*
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu May 02 21:29:40 UTC 2024 - 11.4K bytes - Viewed (0)