Justin Taylor-Barrick

Results 7 issues of Justin Taylor-Barrick

**What would you like to be added**: KUDO frameworks should be tested in many different Kubernetes cluster providers: * GKE * AKS * EKS * kind * MKE * etc....

kind/enhancement
component/testing
kep/4
priority/long-term-important
lifecycle/stale

**What would you like to be added**: The Framework and FrameworkVersions CRDs are namespace scoped, which doesn't make a ton of sense as most likely FrameworkVersions should be provided to...

kind/enhancement
priority/long-term-important
lifecycle/stale
triage/needs-information

**What happened**: https://circleci.com/gh/kudobuilder/kudo/3278?utm_campaign=workflow-failed&utm_medium=email&utm_source=notification ``` 2019/07/22 19:56:18 failed to start the controlplane. retried 5 times: timeout waiting for process etcd to start ``` Looks like I didn't quite get all of...

kind/bug
priority/normal
component/testing
flaky test

**What would you like to be added**: Introduce a `--use-kind` flag that is idempotent, meaning: * if no cluster is running, start one (`--start-kind`) * if a cluster is running,...

enhancement

There are two issues with the built-in kind cluster functionality (that are likely related): 1. If a cluster has no containers running but has not been deleted (e.g., `kind delete...

Currently, the test harness polls for object state when tests are running which offers opportunity for races (and is likely more inefficient). For example, to [test delete steps in KUDO](https://github.com/kudobuilder/kudo/pull/599)...

A mechanism for testing across more than one cluster. Currently, it is only possible to apply manifests or asserts in one cluster for an entire suite, but in some cases...

enhancement