Directories
¶
| Path | Synopsis |
|---|---|
|
This stand-alone package is utilized for dynamically generating/maintaining a list of conformance tests.
|
This stand-alone package is utilized for dynamically generating/maintaining a list of conformance tests. |
|
apimachinery
Package apimachinery contains e2e tests owned by SIG-API-Machinery.
|
Package apimachinery contains e2e tests owned by SIG-API-Machinery. |
|
dra/test-driver/app
Package app does all of the work necessary to configure and run a Kubernetes app process.
|
Package app does all of the work necessary to configure and run a Kubernetes app process. |
|
environment
Package environment contains pre-defined environments used by test/e2e and/or test/e2e_node.
|
Package environment contains pre-defined environments used by test/e2e and/or test/e2e_node. |
|
feature
Package feature contains pre-defined features used by test/e2e and/or test/e2e_node.
|
Package feature contains pre-defined features used by test/e2e and/or test/e2e_node. |
|
framework
Package framework contains provider-independent helper code for building and running E2E tests with Ginkgo.
|
Package framework contains provider-independent helper code for building and running E2E tests with Ginkgo. |
|
framework/config
Package config simplifies the declaration of configuration options.
|
Package config simplifies the declaration of configuration options. |
|
framework/debug/init
Package init sets debug.DumpAllNamespaceInfo as implementation in the framework and enables log size verification and resource gathering.
|
Package init sets debug.DumpAllNamespaceInfo as implementation in the framework and enables log size verification and resource gathering. |
|
framework/metrics/init
Package init installs GrabBeforeEach and GrabAfterEach as callbacks for gathering data before and after a test.
|
Package init installs GrabBeforeEach and GrabAfterEach as callbacks for gathering data before and after a test. |
|
framework/node/init
Package init registers node.AllNodesReady.
|
Package init registers node.AllNodesReady. |
|
framework/testfiles
Package testfiles provides a wrapper around various optional ways of retrieving additional files needed during a test run: - builtin bindata - filesystem access
|
Package testfiles provides a wrapper around various optional ways of retrieving additional files needed during a test run: - builtin bindata - filesystem access |
|
network
Package network are the end-to-end tests for Kubernetes networking.
|
Package network are the end-to-end tests for Kubernetes networking. |
|
nodefeature
Package feature contains pre-defined node features used by test/e2e and/or test/e2e_node.
|
Package feature contains pre-defined node features used by test/e2e and/or test/e2e_node. |
|
storage/podlogs
Package podlogs enables live capturing of all events and log messages for some or all pods in a namespace as they get generated.
|
Package podlogs enables live capturing of all events and log messages for some or all pods in a namespace as they get generated. |
|
upgrades
Package upgrades provides a framework for testing Kubernetes features before, during, and after different types of upgrades.
|
Package upgrades provides a framework for testing Kubernetes features before, during, and after different types of upgrades. |
|
Package e2enode contains e2e tests specific to the node
|
Package e2enode contains e2e tests specific to the node |
|
environment
Build the binary with `go build conformance.go`, then run the conformance binary on a node candidate.
|
Build the binary with `go build conformance.go`, then run the conformance binary on a node candidate. |
|
plugins/gcp-credential-provider
Originally copied from pkg/credentialproviders/gcp
|
Originally copied from pkg/credentialproviders/gcp |
|
remote
Package remote contains implementations of the TestSuite interface, which specify how to run various node test suites remotely.
|
Package remote contains implementations of the TestSuite interface, which specify how to run various node test suites remotely. |
|
runner/remote
To run the node e2e tests remotely against one or more hosts on gce: $ go run run_remote.go --v 2 --ssh-env gce --hosts <comma separated hosts> To run the node e2e tests remotely against one or more images on gce and provision them: $ go run run_remote.go --v 2 --project <project> --zone <zone> --ssh-env gce --images <comma separated images>
|
To run the node e2e tests remotely against one or more hosts on gce: $ go run run_remote.go --v 2 --ssh-env gce --hosts <comma separated hosts> To run the node e2e tests remotely against one or more images on gce and provision them: $ go run run_remote.go --v 2 --project <project> --zone <zone> --ssh-env gce --images <comma separated images> |
|
fuzz
|
|
|
json
Package json implements fuzzers for json deserialization routines in Kubernetes.
|
Package json implements fuzzers for json deserialization routines in Kubernetes. |
|
yaml
Package yaml implements fuzzers for yaml deserialization routines in Kubernetes.
|
Package yaml implements fuzzers for yaml deserialization routines in Kubernetes. |
|
images
|
|
|
agnhost/grpc-health-checking
Package grpchealthchecking offers a tiny grpc health checking endpoint.
|
Package grpchealthchecking offers a tiny grpc health checking endpoint. |
|
agnhost/openidmetadata
Package openidmetadata tests the OIDC discovery endpoints which are part of the ServiceAccountIssuerDiscovery feature.
|
Package openidmetadata tests the OIDC discovery endpoints which are part of the ServiceAccountIssuerDiscovery feature. |
|
agnhost/test-webserver
Package testwebserver offers a tiny web server that serves a static file.
|
Package testwebserver offers a tiny web server that serves a static file. |
|
pets/peer-finder
A small utility program to lookup hostnames of endpoints in a service.
|
A small utility program to lookup hostnames of endpoints in a service. |
|
This stand-alone package is utilized for dynamically generating/maintaining a list of metrics; this list is determined by the stability class of the metric.
|
This stand-alone package is utilized for dynamically generating/maintaining a list of metrics; this list is determined by the stability class of the metric. |
|
documentation
This stand-alone package is utilized for dynamically generating/maintaining documentation on all parseable metrics in the Kubernetes code base.
|
This stand-alone package is utilized for dynamically generating/maintaining documentation on all parseable metrics in the Kubernetes code base. |
|
Package integration provides integration tests for Kubernetes.Some tests require a running etcd or Docker installation on the system.
|
Package integration provides integration tests for Kubernetes.Some tests require a running etcd or Docker installation on the system. |
|
list all unit and ginkgo test names that will be run
|
list all unit and ginkgo test names that will be run |
|
soak
|
|
|
do a fast type check of kubernetes code, for all platforms.
|
do a fast type check of kubernetes code, for all platforms. |
|
format
Package format is an extension of Gomega's format package which improves printing of objects that can be serialized well as YAML, like the structs in the Kubernetes API.
|
Package format is an extension of Gomega's format package which improves printing of objects that can be serialized well as YAML, like the structs in the Kubernetes API. |
|
junit
Package junit provides data structures to allow easy XML encoding and decoding of JUnit test results.
|
Package junit provides data structures to allow easy XML encoding and decoding of JUnit test results. |
|
ktesting
Package ktesting is a wrapper around k8s.io/klog/v2/ktesting.
|
Package ktesting is a wrapper around k8s.io/klog/v2/ktesting. |
|
ktesting/examples/gomega
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag.
|
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag. |
|
ktesting/examples/logging
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag.
|
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag. |
|
ktesting/examples/with_ktesting
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag.
|
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag. |
|
ktesting/examples/without_ktesting
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag.
|
The tests will fail and therefore are excluded from normal "make test" via the "example" build tag. |
Click to show internal directories.
Click to hide internal directories.