Merge pull request #176 from kube-logging/chore/deprecate-fluentd-ver…

…sions

chore: deprecate fluentd versions

.github/workflows/artifacts.yaml

@@ -18,8 +18,6 @@ jobs:
       fail-fast: false
       matrix:
         fluentd:
-          - version: v1.16-4.8
-          - version: v1.16-4.9
           - version: v1.16-4.10
             alias:   v1.16-4.11
           - version: v1.17-5.0

.github/workflows/ci.yaml

@@ -11,8 +11,6 @@ jobs:
       fail-fast: false
       matrix:
         fluentd:
-          - version: v1.16-4.8
-          - version: v1.16-4.9
           - version: v1.16-4.10
             alias:   v1.16-4.11
           - version: v1.17-5.0

README.md

@@ -8,30 +8,38 @@ Pick Fluentd version (either full semver or a shortened major-minor version).
 Pick an image type (`filters` contains filter plugins only, `full` has output plugins as well).
 Image tags are constructed according to the following pattern:
 
-```
+```sh
 ghcr.io/kube-logging/fluentd:VERSION-IMAGE-TYPE
 ```
 
 To ensure that subsequent builds don't break your production environment,
 you may want to pin your image to a specific build:
 
-```
+```sh
 ghcr.io/kube-logging/fluentd:VERSION-IMAGE-TYPE-build.BUILD_NUMBER
 ```
 
 While the tag in the first example is a moving tag (subsequent builds of the same versions produce the same tags),
 build number annotated tags are immutable.
 
 ### Add new plugins
+
 If you wish to add a new plugin, use this image as a base image in your `Dockerfile`:
-```
+
+```dockerfile
 FROM ghcr.io/kube-logging/fluentd:VERSION-IMAGE-TYPE-build.BUILD_NUMBER
 ```
+
 Then add your plugin:
-```
+
+```dockerfile
 RUN fluent-gem install PLUGIN_NAME -v PLUGIN_VERSION
 ```
 
+## Version Support Policy
+
+According to the Logging Operators release-cycle (6 weeks) we maintain the corresponding fluentd image version, which we support for the last 3 releases.
+
 ## Maintenance
 
 Whenever a new Fluentd version is released, check the supported versions and add/remove versions in this repository accordingly.