reflect change in github url (zalando#496)

Project was moved from the incubator to the Zalando main org, hence the rename

Author: FxKu

CONTRIBUTING.md

@@ -5,7 +5,7 @@ Wanna contribute to the Postgres Operator? Yay - here is how!
 ## Reporting issues
 
 If you have a question about patroni or have a problem using it, please read the`README` before filing an issue.
-Also double check with the current issues on our [Issues Tracker](https://github.com/zalando-incubator/postgres-operator/issues).
+Also double check with the current issues on our [Issues Tracker](https://github.com/zalando/postgres-operator/issues).
 
 ## Contributing a pull request
 

README.md

@@ -1,10 +1,10 @@
 # Postgres Operator
 
-[![Build Status](https://travis-ci.org/zalando-incubator/postgres-operator.svg?branch=master)](https://travis-ci.org/zalando-incubator/postgres-operator)
-[![Coverage Status](https://coveralls.io/repos/github/zalando-incubator/postgres-operator/badge.svg)](https://coveralls.io/github/zalando-incubator/postgres-operator)
-[![Go Report Card](https://goreportcard.com/badge/github.com/zalando-incubator/postgres-operator)](https://goreportcard.com/report/github.com/zalando-incubator/postgres-operator)
-[![GoDoc](https://godoc.org/github.com/zalando-incubator/postgres-operator?status.svg)](https://godoc.org/github.com/zalando-incubator/postgres-operator)
-[![golangci](https://golangci.com/badges/github.com/zalando-incubator/postgres-operator.svg)](https://golangci.com/r/github.com/zalando-incubator/postgres-operator)
+[![Build Status](https://travis-ci.org/zalando/postgres-operator.svg?branch=master)](https://travis-ci.org/zalando/postgres-operator)
+[![Coverage Status](https://coveralls.io/repos/github/zalando/postgres-operator/badge.svg)](https://coveralls.io/github/zalando/postgres-operator)
+[![Go Report Card](https://goreportcard.com/badge/github.com/zalando/postgres-operator)](https://goreportcard.com/report/github.com/zalando/postgres-operator)
+[![GoDoc](https://godoc.org/github.com/zalando/postgres-operator?status.svg)](https://godoc.org/github.com/zalando/postgres-operator)
+[![golangci](https://golangci.com/badges/github.com/zalando/postgres-operator.svg)](https://golangci.com/r/github.com/zalando/postgres-operator)
 
 <img src="docs/diagrams/logo.png" width="200">
 
@@ -64,7 +64,7 @@ the rest of the document is a tutorial to get you up and running with the operat
 ## Community      
 
 There are two places to get in touch with the community:
-1. The [GitHub issue tracker](https://github.com/zalando-incubator/postgres-operator/issues)
+1. The [GitHub issue tracker](https://github.com/zalando/postgres-operator/issues)
 2. The #postgres-operator slack channel under [Postgres Slack](https://postgres-slack.herokuapp.com)
 
 ## Quickstart
@@ -82,7 +82,7 @@ built-in Kubernetes support.
 ### Local execution
 
 ```bash
-git clone https://github.com/zalando-incubator/postgres-operator.git
+git clone https://github.com/zalando/postgres-operator.git
 cd postgres-operator
 
 minikube start

build-ci.sh

@@ -1,7 +1,7 @@
 #!/bin/sh
 set -e -x
 
-team_repo="$GOPATH/src/github.com/zalando-incubator/"
+team_repo="$GOPATH/src/github.com/zalando/"
 project_dir="$team_repo/postgres-operator"
 
 mkdir -p "$team_repo"

cmd/main.go

@@ -9,9 +9,9 @@ import (
 	"syscall"
 	"time"
 
-	"github.com/zalando-incubator/postgres-operator/pkg/controller"
-	"github.com/zalando-incubator/postgres-operator/pkg/spec"
-	"github.com/zalando-incubator/postgres-operator/pkg/util/k8sutil"
+	"github.com/zalando/postgres-operator/pkg/controller"
+	"github.com/zalando/postgres-operator/pkg/spec"
+	"github.com/zalando/postgres-operator/pkg/util/k8sutil"
 )
 
 var (

delivery.yaml

@@ -4,7 +4,7 @@ pipeline:
       type: script
       env:
         GOPATH: /root/go
-        OPERATOR_TOP_DIR: /root/go/src/github.com/zalando-incubator
+        OPERATOR_TOP_DIR: /root/go/src/github.com/zalando
       commands:
         - desc: 'Update'
           cmd: |

docs/developer.md

@@ -93,14 +93,14 @@ would create a directory for the GOPATH (i.e. ~/go) and place the source code
 under the ~/go/src subdirectories.
 
 Given the schema above, the postgres operator source code located at
-`github.com/zalando-incubator/postgres-operator` should be put at
--`~/go/src/github.com/zalando-incubator/postgres-operator`.
+`github.com/zalando/postgres-operator` should be put at
+-`~/go/src/github.com/zalando/postgres-operator`.
 
 ```bash
     $ export GOPATH=~/go
-    $ mkdir -p ${GOPATH}/src/github.com/zalando-incubator/
-    $ cd ${GOPATH}/src/github.com/zalando-incubator/
-    $ git clone https://github.com/zalando-incubator/postgres-operator.git
+    $ mkdir -p ${GOPATH}/src/github.com/zalando/
+    $ cd ${GOPATH}/src/github.com/zalando/
+    $ git clone https://github.com/zalando/postgres-operator.git
 ```
 
 ## Building the operator
@@ -157,7 +157,7 @@ The operator employs k8s-provided code generation to obtain deep copy methods an
 the `verify-codegen.sh` checks if the generated code is up-to-date (to be used within CI). The `/pkg/generated/` contains the resultant code. To make these scripts work, you may need to `export GOPATH=$(go env GOPATH)`
 
 References for code generation are:
-* [Relevant pull request](https://github.com/zalando-incubator/postgres-operator/pull/369)
+* [Relevant pull request](https://github.com/zalando/postgres-operator/pull/369)
 See comments there for minor issues that can sometimes broke the generation process.
 * [Code generator source code](https://github.com/kubernetes/code-generator)
 * [Code Generation for CustomResources](https://blog.openshift.com/kubernetes-deep-dive-code-generation-customresources/) - intro post on the topic

docs/gsoc-2019/ideas.md

@@ -6,7 +6,7 @@
 1. Please carefully read the official [Google Summer of Code Student Guide](https://google.github.io/gsocguides/student/) 
 2. Join the #postgres-operator slack channel under [Postgres Slack](https://postgres-slack.herokuapp.com) to introduce yourself to the community and get quick feedback on your application.
 3. Select a project from the list of ideas below or propose your own.
-4. Write a proposal draft.  Please open an issue with the label `gsoc2019_application` in the [operator repository](https://github.com/zalando-incubator/postgres-operator/issues)  so that the community members can publicly review it. See proposal instructions below for details.
+4. Write a proposal draft.  Please open an issue with the label `gsoc2019_application` in the [operator repository](https://github.com/zalando/postgres-operator/issues)  so that the community members can publicly review it. See proposal instructions below for details.
 5. Submit proposal and the proof of enrollment before April 9 2019 18:00 UTC through the web site of the Program.
 
 ## Project ideas 
@@ -34,7 +34,7 @@ It will be helpful to reject erroneous manifests before they reach the operator
 * **Recommended skills**: golang, JSON schema
 * **Difficulty**: medium
 * **Mentor(s)**: Sergey Dudoladov [@sdudoladov](https://github.com/sdudoladov) 
-* **Issue**: [#388](https://github.com/zalando-incubator/postgres-operator/issues/388)
+* **Issue**: [#388](https://github.com/zalando/postgres-operator/issues/388)
 
 ###  Design a solution for the local testing of the operator
 
@@ -45,7 +45,7 @@ A promising option is the Kubernetes own [kind](https://github.com/kubernetes-si
 * **Recommended skills**: Docker, shell scripting, basic Kubernetes abstractions
 * **Difficulty**: medium to hard depending on the selected desing
 * **Mentor(s)**: Dmitry Dolgov [@erthalion](https://github.com/erthalion), Sergey Dudoladov [@sdudoladov](https://github.com/sdudoladov) 
-* **Issue**: [#475](https://github.com/zalando-incubator/postgres-operator/issues/475)
+* **Issue**: [#475](https://github.com/zalando/postgres-operator/issues/475)
 
 ### Detach a Postgres cluster from the operator for maintenance
 
@@ -54,11 +54,11 @@ A promising option is the Kubernetes own [kind](https://github.com/kubernetes-si
 * **Recommended skills**: golang, architecture of a Kubernetes operator
 * **Difficulty**: hard - requires significant modification of the operator's internals and careful consideration of the corner cases.
 * **Mentor(s)**: Dmitry Dolgov [@erthalion](https://github.com/erthalion), Sergey Dudoladov [@sdudoladov](https://github.com/sdudoladov) 
-* **Issue**: [#421](https://github.com/zalando-incubator/postgres-operator/issues/421)
+* **Issue**: [#421](https://github.com/zalando/postgres-operator/issues/421)
 
 ### Propose your own idea
 
 Feel free to come up with your own ideas.  For inspiration, 
-see [our bug tracker](https://github.com/zalando-incubator/postgres-operator/issues), 
+see [our bug tracker](https://github.com/zalando/postgres-operator/issues), 
 the [official `CustomResouceDefinition` docs](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/) 
 and [other operators](https://github.com/operator-framework/awesome-operators).

docs/index.md

@@ -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
 

docs/quickstart.md

@@ -13,7 +13,7 @@ built-in Kubernetes support.
 ## Local execution
 
 ```bash
-git clone https://github.com/zalando-incubator/postgres-operator.git
+git clone https://github.com/zalando/postgres-operator.git
 cd postgres-operator
 
 minikube start

docs/reference/cluster_manifest.md

@@ -3,9 +3,9 @@ Individual postgres clusters are described by the Kubernetes *cluster manifest*
 that has the structure defined by the `postgres CRD` (custom resource
 definition). The following section describes the structure of the manifest and
 the purpose of individual keys. You can take a look at the examples of the
-[minimal](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml)
+[minimal](https://github.com/zalando/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml)
 and the
-[complete](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/complete-postgres-manifest.yaml)
+[complete](https://github.com/zalando/postgres-operator/blob/master/manifests/complete-postgres-manifest.yaml)
 cluster manifests.
 
 When Kubernetes resources, such as memory, CPU or volumes, are configured,

docs/reference/operator_parameters.md

@@ -8,20 +8,20 @@ configuration.
   maps. String values containing ':' should be enclosed in quotes. The
   configuration is flat, parameter group names below are not reflected in the
   configuration structure. There is an
-  [example](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/configmap.yaml)
+  [example](https://github.com/zalando/postgres-operator/blob/master/manifests/configmap.yaml)
 
 * CRD-based configuration. The configuration is stored in a custom YAML
   manifest. The manifest is an instance of the custom resource definition (CRD) called
   `OperatorConfiguration`. The operator registers this CRD
-  during the start and uses it for configuration if the [operator deployment manifest ](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgres-operator.yaml#L21) sets the `POSTGRES_OPERATOR_CONFIGURATION_OBJECT` env variable to a non-empty value. The variable should point to the
+  during the start and uses it for configuration if the [operator deployment manifest ](https://github.com/zalando/postgres-operator/blob/master/manifests/postgres-operator.yaml#L21) sets the `POSTGRES_OPERATOR_CONFIGURATION_OBJECT` env variable to a non-empty value. The variable should point to the
   `postgresql-operator-configuration` object in the operator's namespace.
 
   The CRD-based configuration is a regular YAML
   document; non-scalar keys are simply represented in the usual YAML way.
   There are no default values built-in in the operator, each parameter that is
   not supplied in the configuration receives an empty value.  In order to
   create your own configuration just copy the [default
-  one](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)
+  one](https://github.com/zalando/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)
   and change it.
 
   To test the CRD-based configuration locally, use the following
@@ -245,7 +245,7 @@ CRD-based configuration.
   settings. The default is `1Gi`.
 
 * **set_memory_request_to_limit**
-  Set `memory_request` to `memory_limit` for all Postgres clusters (the default value is also increased). This prevents certain cases of memory overcommitment at the cost of overprovisioning memory and potential scheduling problems for containers with high memory limits due to the lack of memory on Kubernetes cluster nodes. This affects all containers created by the operator (Postgres, Scalyr sidecar, and other sidecars); to set resources for the operator's own container, change the [operator deployment manually](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgres-operator.yaml#L13). The default is `false`.
+  Set `memory_request` to `memory_limit` for all Postgres clusters (the default value is also increased). This prevents certain cases of memory overcommitment at the cost of overprovisioning memory and potential scheduling problems for containers with high memory limits due to the lack of memory on Kubernetes cluster nodes. This affects all containers created by the operator (Postgres, Scalyr sidecar, and other sidecars); to set resources for the operator's own container, change the [operator deployment manually](https://github.com/zalando/postgres-operator/blob/master/manifests/postgres-operator.yaml#L13). The default is `false`.
 
 * **enable_shm_volume**
   Instruct operator to start any new database pod without limitations on shm
@@ -464,4 +464,4 @@ scalyr sidecar. In the CRD-based configuration they are grouped under the
   Memory limit value for the Scalyr sidecar. The default is `1Gi`.
 
 
-For the configmap operator configuration, the [default parameter values](https://github.com/zalando-incubator/postgres-operator/blob/master/pkg/util/config/config.go#L14) mentioned here are likely to be overwritten in your local operator installation via your local version of the operator configmap. In the case you use the operator CRD, all the CRD defaults are provided in the [operator's default configuration manifest](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)
+For the configmap operator configuration, the [default parameter values](https://github.com/zalando/postgres-operator/blob/master/pkg/util/config/config.go#L14) mentioned here are likely to be overwritten in your local operator installation via your local version of the operator configmap. In the case you use the operator CRD, all the CRD defaults are provided in the [operator's default configuration manifest](https://github.com/zalando/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)

docs/user.md

@@ -1,7 +1,7 @@
 ## Create a manifest for a new PostgreSQL cluster
 
 As an example you can take this
-[minimal example](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml):
+[minimal example](https://github.com/zalando/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml):
 
 ```yaml
 apiVersion: "acid.zalan.do/v1"
@@ -68,7 +68,7 @@ In the next sections, we will cover those use cases in more details.
 ## Manifest roles
 
 Manifest roles are defined directly in the cluster manifest. See
-[minimal postgres manifest](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml)
+[minimal postgres manifest](https://github.com/zalando/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml)
 for an example of `zalando` role, defined with `superuser` and `createdb`
 flags.
 
@@ -158,8 +158,8 @@ Since an infrastructure role is created uniformly on all clusters managed by
 the operator, it makes no sense to define it without the password. Such
 definitions will be ignored with a prior warning.
 
-See [infrastructure roles secret](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/infrastructure-roles.yaml)
-and [infrastructure roles configmap](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/infrastructure-roles-configmap.yaml) for the examples.
+See [infrastructure roles secret](https://github.com/zalando/postgres-operator/blob/master/manifests/infrastructure-roles.yaml)
+and [infrastructure roles configmap](https://github.com/zalando/postgres-operator/blob/master/manifests/infrastructure-roles-configmap.yaml) for the examples.
 
 ## Use taints and tolerations for dedicated PostgreSQL nodes
 

glide.yaml

@@ -1,4 +1,4 @@
-package: github.com/zalando-incubator/postgres-operator
+package: github.com/zalando/postgres-operator
 import:
 - package: github.com/sirupsen/logrus
   version: ^1.0.1

hack/update-codegen.sh

@@ -8,6 +8,6 @@ SCRIPT_ROOT=$(dirname ${BASH_SOURCE})/..
 CODEGEN_PKG=${CODEGEN_PKG:-$(cd ${SCRIPT_ROOT}; ls -d -1 ./vendor/k8s.io/code-generator 2>/dev/null || echo ${GOPATH}/src/k8s.io/code-generator)}
 
 vendor/k8s.io/code-generator/generate-groups.sh all \
-  github.com/zalando-incubator/postgres-operator/pkg/generated github.com/zalando-incubator/postgres-operator/pkg/apis \
+  github.com/zalando/postgres-operator/pkg/generated github.com/zalando/postgres-operator/pkg/apis \
   acid.zalan.do:v1 \
   --go-header-file ${SCRIPT_ROOT}/hack/custom-boilerplate.go.txt

mkdocs.yml

@@ -1,5 +1,5 @@
 site_name: Postgres Operator
-repo_url: https://github.com/zalando-incubator/postgres-operator
+repo_url: https://github.com/zalando/postgres-operator
 theme: readthedocs
 
 pages:

pkg/apis/acid.zalan.do/v1/crds.go

@@ -1,7 +1,7 @@
 package v1
 
 import (
-	"github.com/zalando-incubator/postgres-operator/pkg/apis/acid.zalan.do"
+	"github.com/zalando/postgres-operator/pkg/apis/acid.zalan.do"
 	apiextv1beta1 "k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1"
 	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
 )

pkg/apis/acid.zalan.do/v1/operator_configuration_type.go

@@ -1,11 +1,11 @@
 package v1
 
 import (
-	"github.com/zalando-incubator/postgres-operator/pkg/util/config"
+	"github.com/zalando/postgres-operator/pkg/util/config"
 
 	"time"
 
-	"github.com/zalando-incubator/postgres-operator/pkg/spec"
+	"github.com/zalando/postgres-operator/pkg/spec"
 	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
 )
 

pkg/apis/acid.zalan.do/v1/register.go

@@ -5,7 +5,7 @@ import (
 	"k8s.io/apimachinery/pkg/runtime"
 	"k8s.io/apimachinery/pkg/runtime/schema"
 
-	"github.com/zalando-incubator/postgres-operator/pkg/apis/acid.zalan.do"
+	"github.com/zalando/postgres-operator/pkg/apis/acid.zalan.do"
 )
 
 // APIVersion of the `postgresql` and `operator` CRDs