Skip to content

Conversation

@Jan-M
Copy link
Member

@Jan-M Jan-M commented Oct 19, 2017

Working on reorganizing README in favor of getting operator deployed first before focusing on development setup.

@Jan-M Jan-M changed the title Readme 1 Reorganize Readme Oct 19, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 7.898% when pulling ebfad37 on readme-1 into a98c712 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.01%) to 7.887% when pulling ea1ed91 on readme-1 into a98c712 on master.

debug_logging: "true"
dns_name_format: '{cluster}.{team}.staging.{hostedzone}'
docker_image: registry.opensource.zalan.do/acid/demospilo-10:1.3-p2
etcd_host: etcd-client.default.svc.cluster.local:2379
Copy link
Contributor

Choose a reason for hiding this comment

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

It has to be an empty string, otherwise operator will use build-in default: https://github.com/zalando-incubator/postgres-operator/blob/eba23279c8bfce331c85fd5ca58df204568aceb6/pkg/util/config/config.go#L53

  • docker_image versions is p3

$ make docker push

You may define the TAG variable to assign an explicit tag to your docker image and the IMAGE to set the image name.
By default, the tag is computed with `git describe --tags --always --dirty` and the image is `pierone.stups.zalan.do/acid/postgres-operator`
Copy link
Contributor

Choose a reason for hiding this comment

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

Makefile actually contains IMAGE ?= pierone.example.com/acid/postgres-operator

containers:
- name: postgres-operator
image: pierone.stups.zalan.do/acid/postgres-operator:workerassgn
image: registry.opensource.zalan.do/acid/postgres-operator:661b141
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we just use "latest" tag for that?

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 0dc9ba4 on readme-1 into ** on master**.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 453fdbf on readme-1 into ** on master**.

@sdudoladov
Copy link
Member

sdudoladov commented Oct 23, 2017

  1. I think we also need to bump up the Postgres version to "10"
  2. Does serviceaccount.yaml need to mention pierone ?
  3. It is worth mentioning somewhere at the start of the read.me that the whole setup process may take a few minutes. On minikube I observed delays in the pulling of images and allocation of external IP addresses.
  4. It's also worth mentioning the clean way to delete the entire setup, e.g., for starting from scratch, via minikube delete.
  5. The duplicate IMAGE entry in the Makefile should be removed (compare to the line 14)

The last line changes the docker image tag in the manifest to the one the operator image has been built with and removes
the serviceAccountName definition, as the ServiceAccount is not defined in minikube (neither it should, as one has admin
permissions there).
If you perfer to build the image yourself follow up down below.
Copy link
Member

Choose a reason for hiding this comment

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

One can add a link here to the build instructions below. Just a minor convenience.

teams_api_url: http://fake-teams-api.default.svc.cluster.local
workers: "4"
enable_load_balancer: "true"
enable_load_balancer: "false"
Copy link
Member

Choose a reason for hiding this comment

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

That somehow prevents allocation of external IPs for the operator service on minikube. Are there other settings that need to be changed ?

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 0750419 on readme-1 into ** on master**.

@sdudoladov
Copy link
Member

The changes work as of commit 0750419fe: I managed to start Postgres/Spilo as described in the readme within 5 minutes or so.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling ecbd9c0 on readme-1 into ** on master**.

LDFLAGS ?= -X=main.version=$(VERSION)
DOCKERFILE = docker/Dockerfile
IMAGE ?= pierone.example.com/acid/$(BINARY)
IMAGE ?= registry.opensource.zalan.do/acid/$(BINARY)
Copy link
Contributor

Choose a reason for hiding this comment

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

we need registry-write in order to push images

Copy link
Member Author

Choose a reason for hiding this comment

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

It is overwritten in delivery.yaml, I just wanted to remove the pierone references.

@Jan-M
Copy link
Member Author

Jan-M commented Oct 24, 2017

👍

@Jan-M
Copy link
Member Author

Jan-M commented Oct 24, 2017

👍

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 3fb031e on readme-1 into ** on master**.

@CyberDem0n
Copy link
Contributor

👍

@CyberDem0n CyberDem0n merged commit a98a7c9 into master Oct 24, 2017
@erthalion erthalion deleted the readme-1 branch September 13, 2018 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants