Misc updates for next release (#28)

* clean up helm chart

* update this

* missed this

---------

Co-authored-by: Max Williams <[email protected]>

Author: max-rocket-internet

Makefile

@@ -1,5 +1,5 @@
 IMG ?= maxrocketinternet/k8s-event-logger
-TAG ?= 1.9
+TAG ?= 2.0
 PLATFORMS ?= linux/amd64,linux/arm64
 BUILDXDRIVER ?= docker-container
 WITHSBOM ?= true

chart/Chart.yaml

@@ -1,14 +1,12 @@
 apiVersion: v1
-appVersion: "1.9"
+appVersion: "2.0"
 version: "1.2.0"
 description: A tool to log k8s events to stdout in JSON
 home: https://github.com/max-rocket-internet/k8s-event-logger
 name: k8s-event-logger
 maintainers:
 - name: max-rocket-internet
   email: [email protected]
-- name: mmingorance-dh
-  email: [email protected]
 engine: gotpl
 icon: https://github.com/kubernetes/kubernetes/raw/master/logo/logo.png
 keywords:

chart/OWNERS

@@ -1,6 +1,4 @@
 approvers:
 - max-rocket-internet
-- mmingorance-dh
 reviewers:
 - max-rocket-internet
-- mmingorance-dh

chart/README.md

@@ -1,17 +1,6 @@
 # k8s-event-logger
 
-This chart runs a pod that simply watches Kubernetes Events and logs them to stdout in JSON to be collected and stored by your logging solution, e.g. [fluentd](https://github.com/fluent/fluentd-kubernetes-daemonset), [fluent-bit](https://fluentbit.io/), [Filebeat](https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html), or [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/). Other tools exist for persisting Kubernetes Events, such as Sysdig, Datadog, or Google's [event-exporter](https://github.com/GoogleCloudPlatform/k8s-stackdriver/tree/master/event-exporter) but this tool is open and will work with any logging solution.
-
-[Source code](https://github.com/max-rocket-internet/k8s-event-logger)
-
-Events in Kubernetes log very important information. If are trying to understand what happened in the past then these events show clearly what your Kubernetes cluster was thinking and doing. Some examples:
-
-- Pod events like failed probes, crashes, scheduling related information like `TriggeredScaleUp` or `FailedScheduling`
-- HorizontalPodAutoscaler events like scaling up and down
-- Deployment events like scaling in and out of ReplicaSets
-- Ingress events like create and update
-
-The problem is that these events are simply API objects in Kubernetes and are only stored for about 1 hour. Without some way of storing these events, debugging a problem in the past very tricky.
+This chart installs [github.com/max-rocket-internet/k8s-event-logger](https://github.com/max-rocket-internet/k8s-event-logger).
 
 ## Prerequisites
 
@@ -22,7 +11,7 @@ The problem is that these events are simply API objects in Kubernetes and are on
 To install the chart with the release name `my-release` and default configuration:
 
 ```sh
-helm install --name my-release stable/k8s-event-logger
+helm install my-release ./chart
 ```
 
 ## Uninstalling the Chart
@@ -40,8 +29,8 @@ The following table lists the configurable parameters for this chart and their d
 | Parameter                | Description                          | Default                                                |
 | -------------------------|--------------------------------------|--------------------------------------------------------|
 | `resources`              | Resources for the overprovision pods | `{}`                                                   |
-| `image.repository`       | Image repository                     | `maxrocketinternet/k8s-event-logger`                           |
-| `image.tag`              | Image tag                            | `1.8`                                                  |
+| `image.repository`       | Image repository                     | `maxrocketinternet/k8s-event-logger`                   |
+| `image.tag`              | Image tag                            | `2.0`                                                  |
 | `image.pullPolicy`       | Container pull policy                | `IfNotPresent`                                         |
 | `affinity`               | Map of node/pod affinities           | `{}`                                                   |
 | `nodeSelector`           | Node labels for pod assignment       | `{}`                                                   |

chart/values.yaml

@@ -1,6 +1,6 @@
 image:
   repository: maxrocketinternet/k8s-event-logger
-  tag: "1.8"
+  tag: "2.0"
   pullPolicy: IfNotPresent
 
 resources: