-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 kustomize for e2e tests #555
Conversation
Signed-off-by: Yash Khare <[email protected]>
Hi @khareyash05, DetailsInstructions for interacting with me using comments are available here. |
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
/auto-cc |
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
Signed-off-by: Yash Khare <[email protected]>
@@ -54,6 +54,7 @@ function create_cluster() { | |||
kind create cluster --name "${name}" --image "docker.io/kindest/node:${version}" | |||
load_image "${name}" localtest/clustersynchro-manager-amd64:test | |||
load_image "${name}" localtest/apiserver-amd64:test | |||
load_image "${name}" localtest/controller-manager-amd64:test | |||
load_image "${name}" docker.io/bitnami/postgresql:11.15.0-debian-10-r14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clusterpedia/kustomize/internalstorage/postgres/clusterpedia_internalstorage_deployment.yaml
Line 51 in b491fe7
image: postgres:12 |
load_image "${name}" postgres:12
Line 13 in b491fe7
No more need to check helm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
use Kustomize for e2e tests
Does this PR introduce a user-facing change?: