.dir-locals.el

+((yaml-mode . ((eglot-workspace-configuration . ((yaml schemas . ((
+    .yaml_schemas/helm-testsuite-0.7.2.json "tests/**/*"
+))))))))

.gitignore

+charts/*
+!charts/crds/
+!charts/crds/**
+Chart.lock

.gitlab-ci.yml

+image: gitlab-registry.cern.ch/linuxsupport/alma9-base
+
+include:
+  - project : 'ci-tools/container-image-ci-templates'
+    file : 'helm.gitlab-ci.yml'
+    ref: master
+
+stages:
+  - lint
+  - validate
+  - test
+  - build
+  - deploy
+
+docs_lint:
+  stage: lint
+  rules:
+    - if: '$CI_COMMIT_TAG'
+      when: never
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script:
+    - dnf install -y python-pip
+    - python3 -m pip install linkcheckmd
+    - python3 -m linkcheckmd -v README.md
+    - python3 -m linkcheckmd -v docs
+
+yaml_lint:
+  stage: lint
+  rules:
+    - if: '$CI_COMMIT_TAG'
+      when: never
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script:
+    - dnf install -y epel-release
+    - dnf install -y yamllint
+    - yamllint .
+
+helm_lint:
+  stage: lint
+  rules:
+    - if: '$CI_COMMIT_TAG'
+      when: never
+    - if: $CI_PIPELINE_SOURCE == "push"
+  image: alpine/helm
+  script:
+    - helm dep update .
+    - helm lint --strict .
+
+helm_docs_needs_running:
+  stage: validate
+  image: registry.cern.ch/docker.io/jnorwood/helm-docs:v1.14.2
+  rules:
+    - if: '$CI_COMMIT_TAG'
+      when: never
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script:
+    - helm-docs -o test.md
+    - diff -ura test.md README.md
+
+unittest:
+  stage: test
+  image: registry.cern.ch/docker.io/helmunittest/helm-unittest:3.17.0-0.7.2
+  script:
+    - helm unittest -f 'tests/**/*.yaml' .
+
+helm_deploy:
+  stage: deploy
+  image: registry.cern.ch/docker.io/alpine/helm:3
+  rules:
+    - if: '$CI_COMMIT_TAG'
+  script: |
+    sed -i "s/^version:.*/version: ${CI_COMMIT_TAG}/" Chart.yaml
+    helm package .
+    echo ${REGISTRY_PASSWORD} | helm registry login registry.cern.ch -u $REGISTRY_USER --password-stdin
+    helm push cern-it-monitoring-kubernetes-$CI_COMMIT_TAG.tgz oci://registry.cern.ch/monit

.gitlab/merge_request_templates/main_template.md

+### Description
+<!-- Please provide a detailed description of the changes you are proposing. Include the motivation for the change, any new features introduced, and/or bug fixes. -->
+
+### Motivation
+<!-- Why is this change necessary? What issue does it address? -->
+
+### Potential Impact
+<!-- Does this change affect other components or features? Are there any known drawbacks or trade-offs? -->
+
+### Merge Request Checklist
+ - [ ] Documentation has been updated, if applicable.
+ - [ ] Changes have been tested locally using `helm install . ...`.
+
+### Additional Notes <!-- Remove if not required. -->
+<!-- Add any additional notes or context here, such as screenshots, logs, etc., to help reviewers. -->
+

.helmdocsignore

+charts/*
\ No newline at end of file

.helmignore

@@ -4,6 +4,13 @@
 .DS_Store
 # Common VCS dirs
 .git/
+.gitlab-ci-local/
+.gitlab-ci.yml
+.helmignore
+.yamllint
+config
+README.md
+README.md.gotmpl
 .gitignore
 .bzr/
 .bzrignore
@@ -21,3 +28,6 @@
 .idea/
 *.tmproj
 .vscode/
+config
+tests/
+Makefile
\ No newline at end of file

.yamllint

+rules:
+  line-length: disable
+  indentation:
+    spaces: 2
+ignore:
+  - templates/*
+  - charts/crds/crds/*

CHANGELOG.md

+# Change Log
+
+All releases of this chart come with annotated Git tags which serve as
+a change log so please take a look at those if you're looking for
+release notes.

CONTRIBUTING.md

+# Contributing to Kubernetes Monitoring Helm Chart
+
+Thank you for your interest in contributing to the Kubernetes Monitoring Helm Chart project, maintained by the CERN IT Monitoring team. This Helm chart facilitates the collection of both metrics and logs from Kubernetes clusters and the applications running on them. We appreciate your efforts to improve and maintain the chart!
+
+Below are the guidelines to help you contribute effectively.
+
+## How to Contribute
+
+### 1. Fork the Repository
+Begin by creating a fork of the main repository hosted on GitLab at:
+
+`gitlab.cern.ch/monitoring/helm-charts/kubernetes-monitoring`
+
+Forking the repository allows you to freely experiment with changes without affecting the original repository.
+
+### 2. Create a Branch for Your Changes
+Once you've forked the repository, create a feature branch from the `master` branch. A good practice is to name the branch based on the feature or fix you're working on, e.g., `feature/log-enhancement` or `fix/documentation-typo`.
+
+```bash
+git checkout -b feature/my-awesome-feature
+```
+
+### 3. Implement and Test Your Changes
+Develop your changes locally. Please include all the necessary unit tests covering your new feature. Before submitting your contribution, please ensure that you validate your changes thoroughly by running the chart locally.
+
+See [getting started](docs/getting_started.md) for hints on how to install the chart.
+
+This procedure ensures that your changes do not introduce any unintended issues.
+
+### 4. Update Documentation
+If your changes modify or extend the functionality of the chart, do not forget to update the relevant documentation. `README.md` is autogenerated using [helm-docs](https://github.com/norwoodj/helm-docs) so please don't edit this file by hand (modify instead `values.yaml` or `README.md.gotmpl` as needed). Then re-generate the final `README.md` using helm-docs and add those changes too to your change request.
+
+### 5. Submit a Merge Request
+Once your changes are ready, push your branch to your fork and create a Merge Request (MR) targeting the `master` branch of the main repository.
+
+In your MR, provide a clear and detailed explanation of your changes. Include the motivation behind the change, a description of what was modified, and any potential impact or known drawbacks. Make sure to tag the appropriate reviewers from the CERN IT Monitoring team for review.
\ No newline at end of file

Chart.yaml

 apiVersion: v2
 name: cern-it-monitoring-kubernetes
+version: 0.0.0 # DO NOT UPDATE MANUALLY!
 type: application
-appVersion: v0.1.0
-version: 0.1.0
-kubeVersion: ">=1.21.0-0"
-description: Helm Chart provided by IT Monitoring Service to install and configure required components to gather and send monitoring data from kubernetes clusters to central service.
+kubeVersion: ">=1.27.0-0"
+description: Helm Chart provided by the IT Monitoring Service to install and configure the required components to gather and send monitoring data from Kubernetes clusters to the central service.
 home: https://cern.ch/monitoring
 dependencies:
-  - name: prometheus-operator-crds
-    repository: https://prometheus-community.github.io/helm-charts
-    version: 11.0.0
\ No newline at end of file
+  - name: crds
+    version: "0.0.0"
+    condition: crds.enabled

LICENSE

+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2024 European Council for Nuclear Research (CERN)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
\ No newline at end of file

Makefile

+.PHONY: fetch_crds all
+
+# https://github.com/prometheus-community/helm-charts/releases
+VERSION ?= 13.0.2
+
+CRDS_PATH = charts/crds/crds
+URL = https://github.com/prometheus-community/helm-charts/releases/download/prometheus-operator-crds-$(VERSION)/prometheus-operator-crds-$(VERSION).tgz
+
+fetch_crds:
+	rm -rf ${CRDS_PATH}/*.yaml
+	curl -s -L -o - ${URL} | tar -C ${CRDS_PATH} --strip-components=4 -xzf - prometheus-operator-crds/charts/crds/templates
+	find ${CRDS_PATH} -type f -name '*.yaml' -exec sed -i '/{{- with .Values.annotations }}/d' {} +
+	find ${CRDS_PATH} -type f -name '*.yaml' -exec sed -i '/{{- toYaml . | nindent 4 }}/d' {} +
+	find ${CRDS_PATH} -type f -name '*.yaml' -exec sed -i '/{{- end }}/d' {} +
+	sed -i '/^  annotations:/a \    argocd.argoproj.io/sync-options: ServerSideApply=true' ${CRDS_PATH}/*.yaml
+
+all: fetch_crds

README.md.gotmpl

+{{ template "chart.header" . }}
+
+## Description
+
+The **CERN IT Monitoring Kubernetes Helm Chart** provides a solution
+for monitoring Kubernetes clusters at CERN. It enables the collection
+of **metrics**, **logs**, and future support for **traces**, which are
+forwarded to the central CERN monitoring infrastructure. From there
+users can consume them using the day-to-day tools that they already
+user like [Grafana](https://monit-docs.web.cern.ch/access/grafana/) or
+[OpenSearch](https://monit-docs.web.cern.ch/access/opensearch/).
+
+This Helm chart simplifies the deployment and configuration of
+necessary components for observability, making it easier to manage
+monitoring across various Kubernetes clusters and their applications.
+
+## Quick Start
+
+See [getting started](docs/getting_started.md).
+
+{{ template "chart.valuesSection" . }}
+
+## Contributing
+
+We welcome contributions! If you're interested in helping improve this project, please review our [contribution guidelines](CONTRIBUTING.md). In brief:
+
+1. **Fork** the repository.
+2. Create a **feature branch**.
+3. Implement, provide tests and validate your changes.
+4. Submit a **Merge Request (MR)** to the `master` branch.
+
+For a full contribution workflow, visit the [contribution guide](CONTRIBUTING.md).
+
+## Documentation
+
+The main source of documentation for this chart is this
+README. There's some extra details about the components being deployed
+in the [docs](docs) directory, though.
+
+The [MONIT project documentation](https://monit-docs.web.cern.ch)
+contains useful bits complementing this chart.
+
+## License
+
+This repository is licensed under the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0). See the [LICENSE](LICENSE) file for more information.

charts/crds/.helmignore

+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitlab-ci-local/
+.gitlab-ci.yml
+.helmignore
+.yamllint
+config
+README.md
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/
+config
\ No newline at end of file

charts/crds/Chart.yaml

+apiVersion: v2
+name: crds
+version: 0.0.0