Blaine Gardner 9009326ad7 Integration tests: use 'kubectl apply' vs create ...

Some integration tests fail due to resources from a previous integration
run not being cleaned up properly. Instead of using 'kubectl create' --
which fails with an error if the resource already exists -- to create
resources, use 'kubectl apply' -- which does not fail for pre-existing
resources. 'kubectl apply' will give a warning that it should be used to
apply changes to resources created with 'create' or 'apply', but there
is no error.

Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>

2019-08-13 15:03:39 -06:00

..

block.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

cluster.go

api: completed removal of api service

2018-03-16 08:31:34 -07:00

filesystem.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

nfs.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

object_user.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

object.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

pool.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

read_write.go

Integration tests: use 'kubectl apply' vs create

2019-08-13 15:03:39 -06:00

test_client.go

ceph: update the cephcluster custom resource with ceph health

2019-04-10 14:41:18 -06:00