[VAL-74] k8s conformance tests need to have kubectl parameterized Created: 28/Oct/19 Updated: 12/Dec/19 Resolved: 12/Dec/19 |
|
| Status: | Done |
| Project: | Validation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Yolanda Robla Mota | Assignee: | Valentin Radulescu |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The tests are assuming that kubectl is in some binary path. In our kni projects, the kubectl and oc clients are on a requirements folder, because we can have different clients depending on the site. The path to reach kubectl should be configurable. |
| Comments |
| Comment by Armband Enea [ 12/Dec/19 ] |
|
I think that this can be closed. |
| Comment by Naga Sugguna [ 06/Nov/19 ] |
|
As Juha said conformance tests run from one of the https://hub.docker.com/r/akraino/validation/tags?page=1&name=k8s containers. so kubectl is always there on path. /root/.kube/config can be updated as you wish to reach your cluster. |
| Comment by Valentin Radulescu [ 04/Nov/19 ] |
|
Hi, Do you have any update on this issue? Valentin Radulescu |
| Comment by Juha Kosonen [ 29/Oct/19 ] |
|
kubectl is executed in the validation container. So the test does not run kubectl of the cluster side. Or do you mean something else? |