Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove gcr.io/k8s-skaffold repository from examples (GoogleContainerT…
…ools#3368) * Always use the default repository `gcr.io/k8s-skaffold` in tests Signed-off-by: Cornelius Weig <[email protected]> * Remove gcr.io/k8s-skaffold repository from image names Signed-off-by: Cornelius Weig <[email protected]> * Convert former default-repo test to explicit repo tests Signed-off-by: Cornelius Weig <[email protected]> * Adapt image names in examples Signed-off-by: Cornelius Weig <[email protected]> * Revert helm integration test Skaffold deploy with default-repo seems to be not working that way. * Restrict flags to core commands in test-helper Flags such as --namespace or --default-repo are applied to "all" Skaffold commands, but this only applies to all core commands. Make the test helper a bit smarter to not forward unknown arguments. Signed-off-by: Cornelius Weig <[email protected]> * Adapt expectations to account for --default-repo=gcr.io/k8s-skaffold in integration tests Signed-off-by: Cornelius Weig <[email protected]> * Silently ignore unknown flags in integration tests When passing unknown flags to skaffold in integration tests, the tests rightfully fails. However, for simpler test setup it is desirable to unconditionally set some configurations. This change ensures that those flags will not break the integration tests. Signed-off-by: Cornelius Weig <[email protected]> * Use default repo in buildpack example Signed-off-by: Cornelius Weig <[email protected]> * Revert helm-test: use fully qualified image name * Change to fully qualified image in explicit repo integration test
- Loading branch information