This repo houses the Helm charts as well as code and resources that go into the Docker images for a Greenplum on Kubernetes release.
git clone [email protected]:greenplum-db/greenplum-for-kubernetes.git
- Run Unit and Lint Tests
- Deploy Greenplum for Kubernetes on Minikube
- Deploy Greenplum for Kubernetes on GKE
# runs only unit tests
make unit
# runs only linting
make lint
# runs unit and lint
make check
Install Minikube and it's pre-requisites by following instructions
here.
(If there are any problems, use minikube delete to delete the current minikube and then recreate it.)
Use HyperKit with minikube. It's much faster:
brew install docker-machine-driver-hyperkit
# Make sure to follow the `sudo chown` commands that brew outputs
minikube config set vm-driver hyperkitStart minikube as below. You can adjust the resources to be lower if needed, but we recommend these resource settings for improved performance and enabling larger clusters.
minikube start --memory 8192 --cpus 8 --kubernetes-version=v1.16.7 --disk-size 80gConfirm kubectl can access the minikube.
kubectl get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready master 21d v1.10.0Authenticate with gcloud to pull required images from gcr.io
gcloud auth login
gcloud auth configure-dockerRun the following command to change the local docker environment to point to the minikube docker. You only need to run this command once (per shell).
eval $(minikube docker-env)(Note: to undo this docker setting in current shell, run eval "$(docker-machine env -u)")
Then, to build and upload the Greenplum images to minikube's docker registry.
make dockerThe image should now have the tag greenplum-for-kubernetes:<version> as shown below:
$ docker images | grep greenplum
greenplum-operator container-structure-test-in-docker 2de1e0fa79b1 8 minutes ago 928MB
greenplum-operator latest 24ca53fb90aa 8 minutes ago 111MB
greenplum-operator v2.0.0-alpha.2.dev.7.gee6a7552 24ca53fb90aa 8 minutes ago 111MB
greenplum-instance container-structure-test-in-docker b90a82a6a746 10 minutes ago 928MB
greenplum-for-kubernetes latest a2076cf10832 10 minutes ago 2.13GB
greenplum-for-kubernetes v2.0.0-alpha.2.dev.7.gee6a7552 a2076cf10832 10 minutes ago 2.13GBTo clean up images:
# clean files and images directly created by our Makefile
make clean
# clean all the dangling docker images
make docker-cleanOur make deploy target creates a regsecret used by the pods to download images.
This requires a service account key for GCP. You must either place the key in a file named key.json inside the
operator directory or a set the GCP_SVC_ACCT_KEY environment variable for this to work.
To install Greenplum cluster in the minikube environment, run the command below:
make deployYou can access the Greenplum cluster with psql running in master-0:
kubectl exec -it master-0 -- bash -c "source /usr/local/greenplum-db/greenplum_path.sh; psql"If you want to access the Greenplum service outside the minikube and you have a compatible "psql" executable in your path, you can do:
PGPORT=$(minikube service --format "{{.Port}}" --url greenplum) \
PGHOST=$(minikube service --format "{{.IP}}" --url greenplum) \
bash -c 'psql -U gpadmin -h $PGHOST -p $PGPORT'To remove the Greenplum deployment:
make deploy-cleanThe integration tests work by deploying Greenplum for Kubernetes and running checks against the cluster.
Make sure you have performed the Build step before attempting to run the integration tests.
To run integration tests on minikube, execute the following command:
make integrationTo run a specific integration test suite (from greenplum-operator/integration/), run:
make -C greenplum-operator integration-<suite> # e.g. `integration-ha`Create a cluster in GKE either with the web console or on the command line.
Run the following command to set the GKE cluster as your Kubernetes context for the command line
gcloud container clusters get-credentials <your-cluster-name> --project <your-project> --zone <cluster-zone>Confirm kubectl can access the GKE cluster.
kubectl get nodes
NAME STATUS ROLES AGE VERSION
gke-test-default-pool-dba9314c-6xkg Ready <none> 20h v1.15.9-gke.24
gke-test-default-pool-dba9314c-gjxc Ready <none> 20h v1.15.9-gke.24
gke-test-default-pool-dba9314c-s83j Ready <none> 20h v1.15.9-gke.24
gke-test-default-pool-dba9314c-tz4v Ready <none> 20h v1.15.9-gke.24
gke-test-default-pool-dba9314c-wwc6 Ready <none> 20h v1.15.9-gke.24
gke-test-default-pool-dba9314c-x1cq Ready <none> 20h v1.15.9-gke.24Authenticate with gcloud to pull required images from gcr.io
gcloud auth login
gcloud auth configure-dockerThe following command will build the docker images for the Greenplum instance locally and then upload them to GCR so they can be used on your GKE cluster.
make gke-dockerThe image should now have the tag greenplum-for-kubernetes:<version> as shown below:
$ docker images | grep greenplum
greenplum-operator container-structure-test-in-docker 2de1e0fa79b1 8 minutes ago 928MB
greenplum-operator latest 24ca53fb90aa 8 minutes ago 111MB
greenplum-operator v2.0.0-alpha.2.dev.7.gee6a7552 24ca53fb90aa 8 minutes ago 111MB
gcr.io/gp-kubernetes/greenplum-operator dev-24ca53fb90aa 24ca53fb90aa 8 minutes ago 111MB
greenplum-instance container-structure-test-in-docker b90a82a6a746 10 minutes ago 928MB
greenplum-for-kubernetes latest a2076cf10832 10 minutes ago 2.13GB
greenplum-for-kubernetes v2.0.0-alpha.2.dev.7.gee6a7552 a2076cf10832 10 minutes ago 2.13GB
gcr.io/gp-kubernetes/greenplum-for-kubernetes dev-a2076cf10832 a2076cf10832 10 minutes ago 2.13GBA file will be created at /tmp/.gp-kubernetes_gke_image_tags containing the tags of the built images. This file will be used by the make gke-deploy target to reference the correct images.
To clean up images:
# clean files and images directly created by our Makefile
make clean
# clean all the dangling docker images
make docker-cleanOur make gke-deploy target creates a regsecret used by the pods to download images.
This requires a service account key for GCP. You must either place the key in a file named key.json inside the
operator directory or a set the GCP_SVC_ACCT_KEY environment variable for this to work.
To install Greenplum cluster in the GKE environment, run the command below. This will set up parameters for the operator
to use the docker images that were built with the gke-docker target.
make gke-deployYou can access the Greenplum cluster with psql directly through the master pod with:
kubectl exec -it master-0 -- bash -c "source /usr/local/greenplum-db/greenplum_path.sh; psql"To remove the Greenplum deployment:
make gke-deploy-cleanThe integration tests work by deploying Greenplum for Kubernetes and running checks against the cluster.
Make sure you have performed the Build step before attempting to run the integration tests.
To run integration tests on GKE, run the following command:
make gke-integrationTo run a specific integration test suite (from greenplum-operator/integration/), run:
make -C greenplum-operator gke-integration-<suite> # e.g. `gke-integration-ha`![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent