Update maintainers in Dockerfiles and helm chart yaml

Signed-off-by: Vivek Singh <[email protected]>

CONTRIBUTING.md

@@ -57,7 +57,7 @@ Regardless of your familiarity with this project, documentation help is always
 appreciated.
 
 Once you found an issue that interests you, post a comment to the issue, asking
-the maintainers to assign it to you.
+the [maintainers](MAINTAINERS.md) to assign it to you.
 
 ### Coding Standard
 
@@ -128,7 +128,7 @@ discussion
 The pull request template is designed to help you convey this information.
 
 In general, smaller pull requests are easier to review and merge than bigger
-ones. It's always a good idea to collaborate with the maintainers to determine
+ones. It's always a good idea to collaborate with the [maintainers](MAINTAINERS.md) to determine
 how best to break up a big pull request.
 
 Once the maintainers approve your PR, they will label it as `kueue`. The

Dockerfile.in

@@ -9,7 +9,7 @@ LABEL name=ARG_BIN \
       version="${kanister_version}" \
       release="${kanister_version}" \
       summary="Microservice for application-specific data management" \
-      maintainer="Tom Manville<[email protected]>" \
+      maintainer="Kanister maintainers<[email protected]>" \
       description="Frameworks and utilities for application-specific data management, has updated openssl-libs."
 
 RUN microdnf -y update openssl-libs cyrus-sasl-lib && \

GOVERNANCE.md

@@ -11,11 +11,11 @@ to follow the Kanister [Code of Conduct](CODE_OF_CONDUCT.md).
 Contributions to the code base, documentation, or other components in the
 Kanister GitHub organization must follow the guidelines described in the
 [CONTRIBUTING.md](CONTRIBUTING.md) document. Whether these contributions get
-merged into the project is the prerogative of the maintainers.
+merged into the project is the prerogative of the [maintainers](MAINTAINERS.md).
 
 ## Maintainers
 
-Maintainers are responsible for the overall security, quality and integrity of
+[Maintainers](MAINTAINERS.md) are responsible for the overall security, quality and integrity of
 the project. They propose, manage, review, approve/reject major change and
 enhancement requests. They also have the ability to merge code into the project.
 See the [MAINTAINERS.md](MAINTAINERS.md) document for the full list of
@@ -46,5 +46,5 @@ decide whether to grant maintainer status.
 
 This governance is a living document and its policies will need to be updated
 over time to meet the community's needs. Until the steering committee is set
-up, the maintainers will have full ownership of this governance. Changes can be
+up, the [maintainers](MAINTAINERS.md) will have full ownership of this governance. Changes can be
 proposed at any time, but a super majority is required to approve any updates.

README.md

@@ -86,7 +86,7 @@ If you have any questions or run into issues, feel free to reach out to us on
 GitHub issues or pull requests that have been inactive for more than 60 days
 will be labeled as stale. If they remained inactive for another 30 days, they
 will be automatically closed. To be exempted from the issue lifecycle, discuss
-with a maintainer the reasons behind the exemption, and add the `frozen` label
+with a [maintainer](MAINTAINERS.md) the reasons behind the exemption, and add the `frozen` label
 to the issue or pull request.
 
 If you discovered any security issues, refer to our [`SECURITY.md`](SECURITY.md)

SECURITY.md

@@ -9,7 +9,7 @@ You can report a new vulnerability using
 
 Alternatively you can report it via kanisterio google group "Contact owners and managers" button: https://groups.google.com/g/kanisterio/about
 
-The maintainers will help diagnose the severity of the issue and determine how
+The [maintainers](MAINTAINERS.md) will help diagnose the severity of the issue and determine how
 to address the issue. Issues deemed to be non-critical will be filed as GitHub
 issues. Critical issues will receive immediate attention and be fixed as quickly
 as possible. The maintainers will then coordinate a release date with you.

depl.yaml

@@ -0,0 +1,26 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  creationTimestamp: null
+  labels:
+    app: nginx
+    purpose: one
+    purpose: two
+  name: nginx
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: nginx
+  strategy: {}
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - image: nginx
+        name: nginx
+        resources: {}
+status: {}

docker/build/Dockerfile

@@ -1,5 +1,5 @@
 FROM golang:1.23-bullseye
-LABEL maintainer="Tom Manville<[email protected]>"
+LABEL maintainer="Kanister maintainers<[email protected]>"
 
 ARG TARGETPLATFORM
 

docker/cassandra/Dockerfile

@@ -6,7 +6,7 @@ FROM ${TOOLS_IMAGE} AS TOOLS_IMAGE
 # Actual image base
 FROM bitnami/cassandra:5.0.0
 
-MAINTAINER "Tom Manville <[email protected]>"
+MAINTAINER "Kanister maintainers <[email protected]>"
 
 # Install restic to take backups
 COPY --from=TOOLS_IMAGE /usr/local/bin/restic /usr/local/bin/restic

docker/controller/Dockerfile

@@ -1,6 +1,6 @@
 FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5
 
-LABEL maintainer="Tom Manville<[email protected]>"
+LABEL maintainer="Kanister maintainers<[email protected]>"
 
 RUN microdnf -y update openssl-libs
 

docker/couchbase-tools/Dockerfile

@@ -1,6 +1,6 @@
 FROM couchbase:enterprise-7.6.3
 
-MAINTAINER "Tom Manville <[email protected]>"
+MAINTAINER "Kanister maintainers <[email protected]>"
 
 # Install Kanister tools
 RUN apt-get update && apt-get install libdigest-sha-perl -y

docker/foundationdb/Dockerfile

@@ -1,6 +1,6 @@
 FROM foundationdb/foundationdb:6.3.22
 
-MAINTAINER "Tom Manville <[email protected]>"
+MAINTAINER "Kanister maintainers <[email protected]>"
 
 # Install kando 
 RUN curl https://raw.githubusercontent.com/kanisterio/kanister/master/scripts/get.sh | bash

docker/kanister-kubectl/Dockerfile

@@ -7,7 +7,7 @@ LABEL name="kanister-kubectl" \
     vendor="Kanister" \
     version="${kubectl_version}" \
     summary="Kanster tools with kubectl" \
-    maintainer="Tom Manville<[email protected]>"
+    maintainer="Kanister maintainers<[email protected]>"
 
 RUN curl -LO https://storage.googleapis.com/kubernetes-release/release/${kubectl_version}/bin/linux/amd64/kubectl \
     && chmod +x ./kubectl \

docker/kanister-mongodb-replicaset/image/Dockerfile

@@ -1,5 +1,5 @@
 FROM mongo:3.6
-LABEL maintainer="Tom Manville <[email protected]>"
+LABEL maintainer="Kanister maintainers <[email protected]>"
 
 USER root
 

docker/mongodb/Dockerfile

@@ -5,7 +5,7 @@ FROM ${TOOLS_IMAGE} AS TOOLS_IMAGE
 
 FROM bitnami/mongodb:7.0-debian-12
 
-LABEL maintainer="Tom Manville <[email protected]>"
+LABEL maintainer="Kanister maintainers <[email protected]>"
 
 # Update gosu from recent version
 COPY --from=TOOLS_IMAGE /usr/local/bin/gosu /usr/local/bin/gosu

docker/repo-server-controller/Dockerfile

@@ -1,6 +1,6 @@
 FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5
 
-LABEL maintainer="Tom Manville<[email protected]>"
+LABEL maintainer="Kanister maintainers<[email protected]>"
 
 RUN microdnf -y update openssl-libs
 

docker/tools/Dockerfile

@@ -81,7 +81,7 @@ LABEL name="kanister-tools" \
     version="${kan_tools_version}" \
     release="${kan_tools_version}" \
     summary="Operator for data protection workflow management on Kubernetes" \
-    maintainer="Pavan N Devaraj<pavan.n.devaraj@veeam.com>" \
+    maintainer="Kanister maintainers<kanister.maintainers@veeam.com>" \
     description="Tools for application-specific data protection"
 
 COPY --from=builder /restic/restic /usr/local/bin/restic

examples/aws-rds/postgresql/pgtest/Dockerfile.in

@@ -14,7 +14,7 @@
 
 FROM ARG_FROM
 
-MAINTAINER Vaibhav Kamra <[email protected]>
+MAINTAINER Kanister maintainers <[email protected]>
 
 ADD bin/ARG_ARCH/ARG_BIN /ARG_BIN
 

examples/postgres-basic-pgdump/image/Dockerfile

@@ -1,5 +1,5 @@
 FROM postgres:9.6-alpine
-LABEL maintainer="[email protected]"
+LABEL maintainer="[email protected]"
 
 ENV DEBIAN_FRONTEND noninteractive
 

helm/kanister-operator/Chart.yaml

@@ -4,10 +4,8 @@ name: kanister-operator
 version: 0.2.3
 home: https://kanister.io/
 maintainers:
-  - email: [email protected]
-    name: depohmel
-  - email: [email protected]
-    name: tdmanv
+  - email: [email protected]
+    name: Kanister Maintainers
 icon: https://kasten.io/assets/img/kanister-logo.png
 appVersion: 0.112.0
 source: https://github.com/kanisterio/kanister

helm/profile/Chart.yaml

@@ -5,10 +5,8 @@ name: profile
 home: https://kanister.io/
 version: 0.112.0
 maintainers:
-  - email: [email protected]
-    name: tdmanv
-  - email: [email protected]
-    name: depohmel
+  - email: [email protected]
+    name: Kanister Maintainers
 icon: https://kasten.io/assets/img/kanister-logo.png
 appVersion: 0.1.0
 source: https://github.com/kanisterio/kanister

releasenotes/README.md

@@ -18,7 +18,7 @@ When reviewing a PR, a reviewer should check if there are release notes added if
 
 ## Generating changelogs
 
-Changelogs would be generated for each release by maintainers as a part of the release process.
+Changelogs would be generated for each release by [maintainers](../MAINTAINERS.md) as a part of the release process.
 
 Changelog can be generated using: