- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for integration (0.45 sec)
-
istioctl/pkg/tag/revision.go
// MutatingWebhookConfiguration kubernetes object. This is exposed for // integration tests only type MutatingWebhookConfigInfo struct { Name string `json:"name"` Revision string `json:"revision"` Tag string `json:"tag,omitempty"` } // NsInfo represents namespace related information like pods running there. // It is used to display data and is exposed for integration tests. type NsInfo struct {
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sat Jan 28 13:16:05 GMT 2023 - 4.5K bytes - Viewed (0) -
.gitignore
bin/protoc-min-version* bin/protoc-gen-docs* bin/testlinter bin/envvarlinter bin/istioctl *.orig # Avoid accidental istio.VERSION changes istio.VERSION LICENSES.txt # Proxy generated proxy config in integration test tests/integration/component/proxy/envoy.conf **/var/run/secrets/ # Certs generated by testing security/cmd/node_agent/na/cert_file security/cmd/node_agent/na/pkey # istioctl bash completion file tools/istioctl.bash
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Jun 14 16:23:45 GMT 2022 - 1K bytes - Viewed (0) -
bin/update_crds.sh
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 14:28:27 GMT 2024 - 3.4K bytes - Viewed (0) -
RELEASE_BRANCHES.md
at the discretion of the release managers if PRs will be accepted and merged into the release branch. * All code merged in after the feature freeze must have an associated GitHub issue and a release note (exception for unit and integration test changes). * The release managers may not know of all the features being worked on for an Istio release. Developers must make their case as to why their PR should be merged.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Nov 12 23:27:43 GMT 2021 - 3.9K bytes - Viewed (0) -
manifests/charts/README.md
all CRDs to be present. On each upgrade it is recommended to reapply the file, to make sure you get all CRDs. CRDs are separated by release and by component type in the CRD directory. Istio has strong integration with certmanager. Some operators may want to keep their current certmanager CRDs in place and not have Istio modify them. In this case, it is necessary to apply CRD files individually. ```bash
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
CODEOWNERS
/tests/integration/conformance/ @istio/wg-test-and-release-maintainers /tests/integration/framework/ @istio/wg-test-and-release-maintainers /tests/integration/galley/ @istio/wg-networking-maintainers
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 19:22:33 GMT 2024 - 7.2K bytes - Viewed (0) -
common-protos/k8s.io/api/apidiscovery/v2beta1/generated.proto
// For many clients the singular form of the resource will be more understandable to users reading messages and should be used when integrating the name of the resource into a sentence. // The command line tool kubectl, for example, allows use of the singular resource name in place of plurals.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 7.8K bytes - Viewed (0)