[super-agent] remove jobs (#1379)

charts/super-agent/Chart.lock

@@ -5,5 +5,8 @@ dependencies:
 - name: common-library
   repository: https://helm-charts.newrelic.com
   version: 1.1.1
-digest: sha256:b8accc892d1405e664f9b1d47ad5246d9c9c1f266eb003608bc05423f56c4a26
-generated: "2024-01-25T16:36:14.618519184Z"
+- name: super-agent-deployment
+  repository: https://helm-charts.newrelic.com
+  version: 0.0.16-beta
+digest: sha256:c7b1eafa4e10cd193826db2d674e6da9ff7a7f5795991ff316e8f175306bfe0f
+generated: "2024-05-27T14:58:00.756624+02:00"

charts/super-agent/Chart.yaml

@@ -3,7 +3,7 @@ name: super-agent
 description: Bootstraps New Relic' Super Agent
 
 type: application
-version: 0.0.7-beta
+version: 0.0.8-beta
 
 dependencies:
   - name: flux2
@@ -13,6 +13,10 @@ dependencies:
   - name: common-library
     version: 1.1.1
     repository: https://helm-charts.newrelic.com
+  - name: super-agent-deployment
+    version: 0.0.16-beta
+    repository: https://helm-charts.newrelic.com
+    condition: super-agent-deployment.enabled
 
 keywords:
   - newrelic

charts/super-agent/README.md

@@ -2,8 +2,6 @@
 
 # super-agent
 
-![Version: 0.0.6-beta](https://img.shields.io/badge/Version-0.0.6--beta-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
-
 Bootstraps New Relic' Super Agent
 
 # Helm installation
@@ -47,20 +45,8 @@ As of the creation of the chart, it has no particularities and this section can
 | flux2.rbac | object | Enabled (See `values.yaml`) | Create RBAC rules for FluxCD is able to deploy all kind of workloads on the cluster. |
 | flux2.sourceController | object | Enabled | Source controller provides a way to fetch artifacts to the rest of controllers. The source API (which reference [can be read here](https://fluxcd.io/flux/components/source/api/v1/)) is used by admins and various automated operators to offload the Git, OCO, and Helm repositories management. |
 | flux2.watchAllNamespaces | bool | `false` | As we are using Flux as a tool from the super agent to release new workloads, we do not want Flux to listen to all CRs created on the whole cluster. If the user does not want to use Flux and is only using it because of the super agent, this is the way to go so the cluster has deployed all operators needed by the super agent. But if the user want to use Flux for other purposes besides the super agent, this toggle can be used to allow Flux to work on the whole cluster. |
-| helm.create | bool | `true` | Enable the installation of the CRs so FluxCD deploy the Super Agent is deployed. This an advanced/debug flag. It should be always be true unless you know what you are going. |
-| helm.release | object | See `values.yaml` | Values related to the super agent's Helm chart release. |
-| helm.release.chart | string | `"super-agent-deployment"` | The Helm chart of the super-agent. This values is meant to be changed only on air-gapped environments or for development/testing purposes. |
-| helm.release.install | object | See `values.yaml` | Change the behavior of the operator while installing the chart for the first time. This should only be changed by advanced users that know what they are doing. Exposes the remediations that the operator is going to try before give up installing the chart in case it hits an error. |
-| helm.release.rollback | object | See `values.yaml` | Optional configuration of rollback strategy when upgrading. This should only be changed by advanced users that know what they are doing. |
-| helm.release.upgrade | object | See `values.yaml` | Change the behavior of the operator while upgrading the chart. This should only be changed by advanced users that know what they are doing. Exposes the remediations that the operator is going to try before give up installing the chart in case it hits an error. |
-| helm.release.values | string | `{}`. Examples on the `values.yaml` | Set values to the super agent helm release directly from this `values.yaml` file. Refer to https://fluxcd.io/flux/components/helm/helmreleases/#values-overrides |
-| helm.release.valuesFrom | string | empty | Set values from a `configMap` or a `secret`. You can see examples and better documentation inside the `values.yaml` file. Also refer to https://fluxcd.io/flux/components/helm/helmreleases/#values-overrides |
-| helm.release.version | string | `"0.0.12-beta"` | The Helm chart of the super-agent. This values is meant to be changed only on air-gapped environments or for development/testing purposes.  TODO: Point renovatebot here. |
-| helm.repository | object | See `values.yaml` | Values related to the Helm repository where to download the super agent's chart. |
-| helm.repository.certSecretRef | string | `nil` (no secret reference) | secret of type `kubernetes.io/tls` with the standard keys `tls.crt`, `tls.key`, and `ca.crt` |
-| helm.repository.secretRef | string | `nil` (no secret reference) | A reference to a secret with the keys username and password to authenticate to the repository. |
-| helm.repository.updateInterval | string | `"24h"` | Sets the interval the repository is going to be updated on the controller. |
-| helm.repository.url | string | `"https://helm-charts.newrelic.com"` | The repository where the super-agent has the chart. This values is meant to be changed only on air-gapped environments or for development/testing purposes. |
+| super-agent-deployment | object | See `values.yaml` | Values related to the super agent's Helm chart release. |
+| super-agent-deployment.enabled | bool | `true` | Enable the installation of the Super Agent. This an advanced/debug flag. It should be always be true unless  you know what you are going. |
 
 ## Maintainers
 

charts/super-agent/README.md.gotmpl

@@ -3,8 +3,6 @@
 {{ template "chart.header" . }}
 {{ template "chart.deprecationWarning" . }}
 
-{{ template "chart.badgesSection" . }}
-
 {{ template "chart.description" . }}
 
 {{ template "chart.homepageLine" . }}

charts/super-agent/ci/test-values.yaml

@@ -1,5 +1,20 @@
-# chart-testing need values files to test that the chart is installable and upgradable.
-# The values file is needed to be populated. As we have nothing to test for now, I am filling this files with gibberish
-# so the test triggers at the same time that it does not affect the default values file or any other function of the
-# chart of the common library.
-fake: values
+super-agent-deployment:
+  cluster: sa-cluster
+  config:
+    superAgent:
+      content:
+        agents: {}
+    subAgents:
+      test-0:
+        content:
+          a: test
+          value: 0
+      test-1:
+        content:
+          a: test
+          value: 1
+      test-2:
+        content:
+          a: test
+          aYAML:
+            canI: HaveSomeYAML