Merge remote-tracking branch 'origin/master' into bug-fix/less-health-calls

Author: lamai93

CHANGELOG.md

@@ -1,8 +1,25 @@
 # Change Log
 
-## [0.3.10](---) (XXXX-XX-XX)
+## [0.3.11](---) (XXXX-XX-XX)
+- Introduced volume claim templates for all server groups that require volume.
+- Added arangodb-exporter support as sidecar to all arangodb pods.
+- Fixed a bug in the case that all coordinators failed.
+
+
+## [0.3.10](https://github.com/arangodb/kube-arangodb/tree/0.3.10) (2019-04-04)
 - Added Pod Disruption Budgets for all server groups in production mode.
 - Added Priority Class Name to be specified per server group.
+- Forward resource requirements to k8s.
+- Automatic creation of randomized root password on demand.
+- Volume resizing (only enlarge).
+- Allow to disable liveness probes, increase timeouts in defaults.
+- Handle case of all coordinators gone better.
+- Added `MY_NODE_NAME` and `NODE_NAME` env vars for all pods.
+- Internal communications with ArangoDB more secure through tokens which
+  are limited to certain API paths.
+- Rolling upgrade waits till all shards are in sync before proceeding to
+  next dbserver, even if it takes longer than 15 min.
+- Improve installation and upgrade instructions in README.
 
 ## [0.3.9](https://github.com/arangodb/kube-arangodb/tree/0.3.9) (2019-02-28)
 [Full Changelog](https://github.com/arangodb/kube-arangodb/compare/0.3.8...0.3.9)

MAINTAINERS.md

@@ -2,20 +2,35 @@
 
 ## Running tests
 
-To run the entire test set, run:
+To run the entire test set, first set the following environment variables:
+
+  - `DOCKERNAMESPACE` to your docker hub account
+  - `VERBOSE` to `1` (default is empty)
+  - `LONG` to `1` (default is empty, which skips lots of tests)
+  - `ARANGODB` to the name of a community image you want to test,
+    default is `arangodb/arangodb:latest`
+  - `ENTERPRISEIMAGE` to the name of an enterprise image, you want to
+    test, if not set, some tests are skipped
+  - `ARANGO_LICENSE_KEY` to the enterpise license key
+  - `KUBECONFIG` to the path to some k8s configuration with
+    credentials, this indicates which cluster to use
 
 ```bash
-export DOCKERNAMESPACE=<your docker hub account>
 make clean
 make build
 make run-tests
 ```
 
+To run only a single test, set `TESTOPTIONS` to something like
+`-test.run=TestRocksDBEncryptionSingle` where
+`TestRocksDBEncryptionSingle` is the name of the test.
+
 ## Preparing a release
 
 To prepare for a release, do the following:
 
 - Make sure all tests are OK.
+- To run a complete set of tests, see above.
 - Update the CHANGELOG manually, since the automatic CHANGELOG
   generation is switched off (did not work in many cases).
 

README.md

@@ -37,32 +37,79 @@ it is intended to be.
 | Docker for Mac Edge  | 1.10               | >= 3.3.13        | Runs  | Not intended     |                       |
 | Scaleway Kubernetes  | 1.10               | >= 3.3.13        | ?     | No               |                       |
 
-## Installation of latest release using Helm
+## WARNING
 
 **WARNING**: There is a problem with rolling upgrades in version 0.3.8.
 **DO NOT USE 0.3.8 FOR ROLLING UPGRADES.** If you are still using 0.3.8,
 then upgrade to 0.3.9 of the operator first before running any rolling
 upgrade.
 
+## Installation of latest release using Kubectl
+
+```bash
+kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.10/manifests/arango-crd.yaml
+kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.10/manifests/arango-deployment.yaml
+# To use `ArangoLocalStorage`, also run
+kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.10/manifests/arango-storage.yaml
+# To use `ArangoDeploymentReplication`, also run
+kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.10/manifests/arango-deployment-replication.yaml
+```
+
+This procedure can also be used for upgrades and will not harm any
+running ArangoDB deployments.
+
+## Installation of latest release using Helm
+
+Only use this procedure for a new install of the operator. See below for
+upgrades.
+
 ```bash
 # The following will install the custom resources required by the operators.
-helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.9/kube-arangodb-crd.tgz
+helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.10/kube-arangodb-crd.tgz
 # The following will install the operator for `ArangoDeployment` &
 # `ArangoDeploymentReplication` resources.
-helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.9/kube-arangodb.tgz
+helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.10/kube-arangodb.tgz
 # To use `ArangoLocalStorage`, also run
-helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.9/kube-arangodb-storage.tgz
+helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.10/kube-arangodb-storage.tgz
 ```
 
-## Installation of latest release using Kubectl
+## Upgrading the operator using Helm
+
+To upgrade the operator to the latest version with Helm, you have to
+delete the previous deployment and then install the latest. **HOWEVER**:
+You *must not delete* the deployment of the custom resource definitions
+(CRDs), or your ArangoDB deployments will be deleted!
+
+Therefore, you have to use `helm list` to find the deployments for the
+operator (`kube-arangodb`) and of the storage operator
+(`kube-arangodb-storage`) and use `helm delete` to delete them using the
+automatically generated deployment names. Here is an example of a `helm
+list` output:
+
+```
+% helm list
+NAME            	REVISION	UPDATED                 	STATUS  	CHART                               	APP VERSION	NAMESPACE
+intent-camel    	1       	Mon Apr  8 11:37:52 2019	DEPLOYED	kube-arangodb-storage-0.3.10-preview	           	default  
+steely-mule     	1       	Sun Mar 31 21:11:07 2019	DEPLOYED	kube-arangodb-crd-0.3.9             	           	default  
+vetoed-ladybird 	1       	Mon Apr  8 11:36:58 2019	DEPLOYED	kube-arangodb-0.3.10-preview        	           	default  
+```
+
+So here, you would have to do
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.9/manifests/arango-crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.9/manifests/arango-deployment.yaml
+helm delete intent-camel
+helm delete vetoed-ladybird
+```
+
+but **not delete `steely-mule`**. Then you could install the new version
+with `helm install` as normal:
+
+```bash
+# The following will install the operator for `ArangoDeployment` &
+# `ArangoDeploymentReplication` resources.
+helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.10/kube-arangodb.tgz
 # To use `ArangoLocalStorage`, also run
-kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.9/manifests/arango-storage.yaml
-# To use `ArangoDeploymentReplication`, also run
-kubectl apply -f https://raw.githubusercontent.com/arangodb/kube-arangodb/0.3.9/manifests/arango-deployment-replication.yaml
+helm install https://github.com/arangodb/kube-arangodb/releases/download/0.3.10/kube-arangodb-storage.tgz
 ```
 
 ## Building

VERSION

@@ -1 +1 @@
-0.3.9+git
+0.3.11-preview