You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 6, 2025. It is now read-only.
This repo contains the code needed to run Gaffer using Docker or Kubernetes.
4
-
There are two main sub-folders, 'docker' and 'kubernetes' which contain the project files you need for starting Gaffer using those services.
4
+
There are two main sub-folders, 'docker' and 'kubernetes', which contain the
5
+
project files you need for starting Gaffer using those services.
5
6
6
-
# Running Gaffer Using Docker
7
+
##Running Gaffer Using Docker
7
8
8
-
For information on how to run Gaffer using Docker containers, please see the documentation: [Gaffer Docker Docs](https://gchq.github.io/gaffer-doc/latest/dev/docker/)
9
+
For information on how to run Gaffer using Docker containers please see the
We also provide some example deployments with different store backings
13
+
to help you get started learning and testing Gaffer. Please see the
14
+
[example deployments](./docker/example-deployments/) directory for more
15
+
details.
11
16
12
-
For information on how to run Gaffer using Kubernetes, please see the documentation: [Gaffer Kubernetes Docs](https://gchq.github.io/gaffer-doc/latest/dev/kubernetes-guide/kubernetes/)
17
+
## Running Gaffer Using Kubernetes
13
18
14
-
# Versioning
19
+
For information on how to run Gaffer using Kubernetes, please see the
Each of our images which is released will be tagged with the version of the software they represent. Every release,
17
-
we update the `latest` tag for each image and add a new release which has the corresponding version tag.
22
+
## Versioning
23
+
24
+
Each of the released images will be tagged with the version of the
25
+
software they represent. Every release we update the `latest` tag for each
26
+
image and add a new release which has the corresponding version tag.
18
27
19
28
If we release Gaffer version 2.1.2, the following images would be uploaded:
20
29
@@ -24,17 +33,20 @@ If we release Gaffer version 2.1.2, the following images would be uploaded:
24
33
- gchq/gaffer:2.1.2
25
34
- gchq/gaffer:2.1.2-accumulo-2.0.1
26
35
27
-
We maintain mutable versions of latest, as well as the major, minor and bugfix versions of Gaffer. For reproducibility
28
-
make sure to use the full version in your build metadata. For `gaffer`/`gaffer-rest` images, we also create a tag including the
29
-
accumulo version, this allows for compatibility with Accumulo 1.9.3 in our tests. The `-accumulo-1.9.3` tagged images
30
-
are not published but can be build locally if required.
36
+
We maintain mutable versions of latest, as well as the major, minor and bugfix
37
+
versions of Gaffer. For reproducibility make sure to use the full version in
38
+
your build metadata. For `gaffer`/`gaffer-rest` images, we also create a tag
39
+
including the accumulo version, this allows for compatibility with Accumulo
40
+
1.9.3 in our tests. The `-accumulo-1.9.3` tagged images are not published but
41
+
can be built locally if required.
31
42
32
43
The release process is automated by GitHub actions.
33
44
34
-
# Known Compatible Docker Versions
45
+
##Known Compatible Docker Versions
35
46
36
47
- 20.10.23
37
48
38
-
# Contributing
49
+
##Contributing
39
50
40
-
We welcome contributions to this project. Detailed information on our ways of working can be found in our [developer docs](https://gchq.github.io/gaffer-doc/latest/dev/ways-of-working/).
51
+
We welcome contributions to this project. Detailed information on our ways of
52
+
working can be found in our [developer docs](https://gchq.github.io/gaffer-doc/latest/development-guide/ways-of-working.html).
0 commit comments