Closed vdice closed 7 years ago
Turns out the errors described above were a result of using an older version of k8s (1.4.6) -- PR has been issued to update this version: https://github.com/deis/workflow-e2e/pull/361
Will update this issue if anything actually related to RBAC + e2e is found; otherwise will close.
Interestingly, the only test failure I am reliably seeing now when running against a Workflow install w/ global.use_rbac=true
is the user can run a command with lengthy output in that app's environment
test which I've actually been trying to amend in https://github.com/deis/workflow-e2e/pull/363
Closing for now; I don't see any amendments needed at this time. (error described in https://github.com/deis/workflow-e2e/issues/358#issuecomment-305037560 can also be hit on non-RBAC clusters.)
Currently, e2e doesn't run against a Workflow install with RBAC enabled (would need to
--set global.use_rbac=true
). (See https://github.com/deis/workflow/pull/812 for addition, scheduled for v2.15)However, if/when we decided to do so, there appear to be the following changes/amendments needed (seen testing locally):
Lines like this one in the tags tests error out with the following:
Same for similar
kubectl
invocations in the limits tests.Other?