Tomas Kral
Tomas Kral
What if we put this on the lowest priority? We can implement this only once it's clear this is really needed by some real use case.
related to #326 and the same comment here: This applies to `kedge init`
This is still valid > Also, could you explain more on what sort of questions do we want to be a part of this? Questions like: - How is Kedge...
> For a user who is only dealing with Kubernetes and has no clue of OpenShift, how do we facilitate that she does not mix the OpenShift artifacts in between?...
I thought that we are officially supporting only Kubernetets 1.6 and up and OpenShift 3.6 and up. This should be stated in Readme somewhere. If not that we have to...
Can you show an example how it would improve our tests? I don't think that current state of the tests is a fault of the standard testing library. But more...
can you show example where it is going to help in our tests? how it is different from doing ```go if A != B { return fmt.Errof("A is not equal...
big +1 it is impossible to find anything useful in current output. verbose output should be dumped only if there is an error
semaphore e2e tests are still verbose. It is really hard to find out why the test is failing in all that input. I really like `go test` behavior, if everything...
We should also clean up errors, that are actually not errors, like showing ``` 0: dial tcp 192.168.122.112:31850: getsockopt: connection refused e2e_test.go:217: error while making http request "http://192.168.122.112:31850" for service...