The GetInstanceGroup function was used in kubetest2-tester-kops which has the desired `kops` set in PATH and KOPS_STATE_STORE already set.
Now that we're using GetInstanceGroups in kubetest2-kops (the deployer) we need to override these to the values that the deployer determines.
If we specify a zone to the e2e tests, it will try to pre-provision
volumes into it for the inline tests. We then will be unable to
attach a volume to test pods if we don't have (normal) nodes in that
zone.
Pick a zone that is schedulable for test pods.
This will move the logic from build_jobs.py into kubetest2 itself.
This way we can rely on this logic from scenario scripts and other places that arent directly set by build_jobs.py.
Add create-args parameter only once with spaces separating multiple arguments
Add kops state store
Another fix to check if environment variable are used correctly
Add state store for digital ocean
Add env variables for do related job
check if env is empty
tmp check 1
Revert changes
Use a smaller droplet size
Update make file
Add SSH key for DO
Add private key path
update ssh user
Another fix
try with v1.18
use 1.20
Rebase with master
Fix merge issues
Add DO droplet dump support
I'm hoping this allows our e2e tests to dump system logs into the job artifacts for easier troubleshooting
Use root ssh user
use 2 nodes to reduce cost
another minor fix
Skip services test
Increase master size
Skip flaky tests
Remove pod status test that belongs to v1.20
Add do test file and revert changes to make file
Update make file
Include DigitalOcean in the supported provider flags
incorporate review comments
Update tests/e2e/pkg/tester/tester.go
Co-authored-by: Peter Rifel <rifelpet@users.noreply.github.com>
Fix formatting
Add higher resource master and nodes for running e2e tests
Revert back to use lower size masters
This argument was required for the tests to pass prior to 1.18, so we
should still pass it if we want these tests to pass.
We can infer it from kubeconfig (that is the fix that was introduced in 1.18)