Check for tools rather than install them

Different systems use different package managers.

Author: cbandy

Makefile

@@ -3,10 +3,8 @@
 ANSIBLE_VERSION ?= 2.9.*
 PGOROOT ?= $(CURDIR)
 PGO_BASEOS ?= centos7
-PGO_CMD ?= kubectl
 PGO_IMAGE_PREFIX ?= crunchydata
 PGO_IMAGE_TAG ?= $(PGO_BASEOS)-$(PGO_VERSION)
-PGO_OPERATOR_NAMESPACE ?= pgo
 PGO_VERSION ?= 4.5.0
 PGO_PG_VERSION ?= 12
 PGO_PG_FULLVERSION ?= 12.4
@@ -104,6 +102,7 @@ installrbac:
 
 setup:
 PGOROOT='$(PGOROOT)' ./bin/get-deps.sh
+./bin/check-deps.sh
 
 setupnamespaces:
 PGOROOT='$(PGOROOT)' ./deploy/setupnamespaces.sh

bin/check-deps.sh

@@ -0,0 +1,38 @@
+#!/bin/bash -e
+
+# Copyright 2020 Crunchy Data Solutions, Inc.
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+echo "Ensuring project dependencies..."
+
+if ! command -v go &> /dev/null; then
+echo 'Cannot find `go`. Perhaps:'
+echo ' sudo yum install golang'
+exit 1
+fi
+if ! sort -VC <<< $'go1.13\n'"$( read -ra array <<< "$(go version)"; echo "${array[2]-}" )"; then
+echo 'Old version of `go`: «' "$(go version)" '» Perhaps:'
+echo ' sudo yum update golang'
+exit 1
+fi
+
+if ! command -v buildah &> /dev/null; then
+echo 'Cannot find `buildah`. Perhaps:'
+echo ' sudo yum install buildah'
+exit 1
+fi
+if ! sort -VC <<< $'1.14.9\n'"$( read -ra array <<< "$(buildah --version)"; echo "${array[2]-}" )"; then
+echo 'Old version of `buildah`: «' "$(buildah --version)" '» Perhaps:'
+echo ' sudo yum update buildah'
+exit 1
+fi

bin/get-deps.sh

@@ -13,64 +13,19 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-echo "Ensuring project dependencies..."
+echo "Getting project dependencies..."
 BINDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
 EVTDIR="$BINDIR/pgo-event"
 POSTGRES_EXPORTER_VERSION=0.8.0
 
 
-# Idempotent installations
-if (yum repolist | egrep -q '^epel/') ; then
-echo "Confirmed EPEL repo exists..."
-else
-echo "=== Installing EPEL ==="
-# Prefer distro-managed epel-release if it exists (e.g. CentOS)
-if (yum -q list epel-release 2>/dev/null); then
-sudo yum -y install epel-release
-else
-sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-fi
-fi
-
-if which go; then
-echo -n " Found: " && go version
-else
-echo "=== Installing golang ==="
-sudo yum -y install golang
-fi
-
 if ! [ -f $EVTDIR/nsqd -a -f $EVTDIR/nsqadmin ]; then
 echo "=== Installing NSQ binaries ==="
 NSQ=nsq-1.1.0.linux-amd64.go1.10.3
 curl -S https://s3.amazonaws.com/bitly-downloads/nsq/$NSQ.tar.gz | \
 tar xz --strip=2 -C $EVTDIR/ '*/bin/*'
 fi
 
-if which docker; then
-# Suppress errors for this call, as docker returns non-zero when it can't talk to the daemon
-set +e
-echo -n " Found: " && docker version --format '{{.Client.Version}}' 2>/dev/null
-set -e
-else
-echo "=== Installing docker ==="
-if [ -f /etc/centos-release ]; then
-sudo yum -y install docker
-else
-sudo yum -y install docker --enablerepo=rhel-7-server-extras-rpms
-fi
-fi
-
-if which buildah; then
-echo -n " Found: " && buildah --version
-else
-echo "=== Installing buildah ==="
-if [ -f /etc/centos-release ]; then
-sudo yum -y install buildah
-else
-sudo yum -y install buildah --enablerepo=rhel-7-server-extras-rpms
-fi
-fi
-
 # Download Postgres Exporter, only required to build the Crunchy Postgres Exporter container
 wget -O $PGOROOT/postgres_exporter.tar.gz https://github.com/wrouesnel/postgres_exporter/releases/download/v${POSTGRES_EXPORTER_VERSION?}/postgres_exporter_v${POSTGRES_EXPORTER_VERSION?}_linux-amd64.tar.gz
 

docs/content/contributing/developer-setup.md

@@ -12,7 +12,7 @@ This guide is intended for those wanting to build the Operator from source or co
 
 # Prerequisites
 
-The target development host for these instructions is a CentOS 7 or RHEL 7 host. Others operating systems
+The target development host for these instructions is a CentOS 8 or RHEL 8 host. Others operating systems
 are possible, however we do not support building or running the Operator on others at this time.
 
 ## Environment Variables
@@ -23,11 +23,6 @@ Variable | Example | Description
 -------- | ------- | -----------
 `PGOROOT` | $HOME/postgres-operator | Operator repository location
 `PGO_CONF_DIR` | $PGOROOT/installers/ansible/roles/pgo-operator/files | Operator Config Template Directory
-`PGO_BASEOS` | {{< param centosBase >}} | Base OS for container images
-`PGO_CMD` | kubectl | Cluster management tool executable
-`PGO_IMAGE_PREFIX` | crunchydata | Container image prefix
-`PGO_OPERATOR_NAMESPACE` | pgo | Kubernetes namespace for the operator
-`PGO_VERSION` | {{< param operatorVersion >}} | Operator version
 
 {{% notice tip %}}
 `examples/envs.sh` contains the above variable definitions as well as others used by postgres-operator tools
@@ -36,10 +31,9 @@ Variable | Example | Description
 
 ## Other requirements
 
-* The development host has been created, has access to `yum` updates, and has a regular user account with `sudo` rights to run `yum`.
 * The development host has `git` installed and has cloned the [postgres-operator](https://github.com/CrunchyData/postgres-operator.git) repository. Makefile targets below are run from the repository directory.
 * Deploying the Operator will require deployment access to a Kubernetes or OpenShift cluster
-* Once you have cloned the git repository, you will need to download the CentOS 7 repository files and GPG keys and place them in the `$PGOROOT/conf` directory. You can do so with the following code:
+* Once you have cloned the git repository, you will need to download the CentOS repository files and GPG keys and place them in the `$PGOROOT/conf` directory. You can do so with the following code:
 
 ```shell
 cd $PGOROOT
@@ -58,14 +52,10 @@ Configuring build dependencies is automated via the `setup` target in the projec
 
 The setup target ensures the presence of:
 
-* EPEL yum repository
 * [`go`](https://golang.org/) compiler version 1.13+
 * NSQ messaging binaries
-* `docker` container tool
 * `buildah` OCI image building tool version 1.14.9+
 
-By default, docker is not configured to run its daemon. Refer to the [docker post-installation instructions](https://docs.docker.com/install/linux/linux-postinstall/) to configure it to run once or at system startup. This is not done automatically.
-
 ## Code Generation
 
 Code generation is leveraged to generate the clients and informers utilized to interact with the
@@ -110,17 +100,7 @@ After a full compile, you will have a `pgo` binary in `$PGOROOT/bin` and the Ope
 # Deployment
 
 Now that you have built the PostgreSQL Operator images, you can now deploy them
-to your Kubernetes cluster. To deploy the image and associated Kubernetes
-manifests, you can execute the following command:
-
-```shell
-make deployoperator
-```
-
-If your Kubernetes cluster is not local to your development host, you will need
-to specify a config file that will connect you to your Kubernetes cluster. See
-the [Kubernetes documentation](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/)
-for details.
+to your Kubernetes cluster by following the [Bash Installation Guide]({{< relref "installation/other/bash.md" >}}).
 
 # Testing