Connect to the clusters declared with -kube or on KUBECONFIG This can be called many times, but will be only executed once.

Execute helps executing commands on a given pod, using the k8s rest api returning stdout, stderr, err This function is nil safe and so stdout and stderr are always returned This is copied straight from skupper test/utils/k8s/execute.go Do not use this out of f2k8s.

Flag adds the flag "-kube" to the list of flags to be parsed on the command line; call it right before flag.Parse(), on TestMain, if you want your test to interact with multiple Kubernetes clusters.

ParseContext will parse the provided value, with the format [kind=]/path/to/file.

This will simply create a namespace on the given cluster, with the requested name.

This creates a K8S namespace, based on a TestBase; the namespace name will include the provided Id, but it will also contain other information (such as the TestBase Id, a sequence number, etc) The namespace also receives a label frame2.id, with which it is easy to identify (and possibly modify or remove) any namespaces created by a test run.

This is a direct call to K8S to remove a namespace.

TODO: make this an Executor?.

This is to be used as an embedded field; implement the whole of Namespacer here Consider this: the PodInterface below (and others) might be interesting, but they'd pollute the frame's namespace if embedded This is not a frame: not an executor or a validator.

This contains a list of namespaces to be used by the test Use NewTestBase() as a constructor.

The type of cluster: - Public - Private - DMZ Currently, only the first two are implemented.