mirror of
https://github.com/zalando/postgres-operator.git
synced 2026-10-17 21:13:31 +02:00
reflect change in github url (#496)
Project was moved from the incubator to the Zalando main org, hence the rename
This commit is contained in:
committed by
Sergey Dudoladov
parent
26a7fdfa9f
commit
31e568157b
+3
-3
@@ -8,10 +8,10 @@ manages PostgreSQL clusters on Kubernetes:
|
||||
user submits a new manifest, the operator fetches that manifest and spawns a
|
||||
new Postgres cluster along with all necessary entities such as Kubernetes
|
||||
StatefulSets and Postgres roles. See this
|
||||
[Postgres cluster manifest](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/complete-postgres-manifest.yaml)
|
||||
[Postgres cluster manifest](https://github.com/zalando/postgres-operator/blob/master/manifests/complete-postgres-manifest.yaml)
|
||||
for settings that a manifest may contain.
|
||||
|
||||
2. The operator also watches updates to [its own configuration](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/configmap.yaml)
|
||||
2. The operator also watches updates to [its own configuration](https://github.com/zalando/postgres-operator/blob/master/manifests/configmap.yaml)
|
||||
and alters running Postgres clusters if necessary. For instance, if a pod
|
||||
docker image is changed, the operator carries out the rolling update. That
|
||||
is, the operator re-spawns one-by-one pods of each StatefulSet it manages
|
||||
@@ -47,7 +47,7 @@ the operator is deployed to multiple Kubernetes clusters, where users deploy
|
||||
manifests via our CI/CD infrastructure or rely on a slim user interface to
|
||||
create manifests.
|
||||
|
||||
Please, report any issues discovered to https://github.com/zalando-incubator/postgres-operator/issues.
|
||||
Please, report any issues discovered to https://github.com/zalando/postgres-operator/issues.
|
||||
|
||||
## Talks
|
||||
|
||||
|
||||
Reference in New Issue
Block a user