Skip to content
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

Fix run operator locally #462

Merged
merged 3 commits into from
Jan 29, 2019
Merged

Fix run operator locally #462

merged 3 commits into from
Jan 29, 2019

Conversation

sdudoladov
Copy link
Member

  1. Bump up Spilo and operator images
  2. Run acid-minimal-cluster in the default namespace, add an option to run it in test
  3. Fix the command for starting minikube (caused by changes in its API)
  4. Add an option to replace the operator image without restarting the minikube; that greatly speeds up local testing as minikube restarts may take minutes.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 23.766% when pulling 35803a8 on fix-run-operator-locally into 6f6a599 on master.

@sdudoladov sdudoladov merged commit 43e8288 into master Jan 29, 2019
@@ -10,7 +10,7 @@ data:

debug_logging: "true"
workers: "4"
docker_image: registry.opensource.zalan.do/acid/spilo-cdp-11:1.5-p42
docker_image: registry.opensource.zalan.do/acid/spilo-11:1.5-p4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sdudoladov , just curious what is the difference between spilo-cdp-11 and spilo-11?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

spilo-cdp is build and pushed by ci/cd system on every commit to the master branch.
Later it is tested and if everything is fine we are tagging it as a spilo.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is spilll-11 aligned with Patroni releases or it is for every commit as well, just after test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants