Only render configmap if resourceClasses are set

README.md

@@ -90,7 +90,7 @@ The command removes all the Kubernetes objects associated with the chart and del
 | agent.readinessProbe.successThreshold | int | `1` |  |
 | agent.readinessProbe.timeoutSeconds | int | `1` |  |
 | agent.replicaCount | int | `1` |  |
-| agent.resourceClasses | object | `{}` | Resource class settings. The tokens specified here will be used to claim tasks & the tasks will be launched with the configured configs Ref: https://circleci.com/docs/container-runner/#resource-class-configuration-custom-pod |
+| agent.resourceClasses | object | `{}` | Resource class settings. The tokens specified here will be used to claim tasks & the tasks will be launched with the configured configs If you leave this unset you must provide your own configmap named {{ include "container-agent.fullname" . }} Ref: https://circleci.com/docs/container-runner/#resource-class-configuration-custom-pod |
 | agent.resources | object | `{}` | Agent pod resource configuration Ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ |
 | agent.runnerAPI | string | `"https://runner.circleci.com"` | CircleCI Runner API URL |
 | agent.serviceContainers | object | `{}` | Configuration for service containers. This allows different a different container spec to be passed to your job's service containers. TODO: Full docs link |

changelog.md

@@ -2,6 +2,8 @@
 
 # Edge
 
+[#81](https://github.com/CircleCI-Public/container-runner-helm-chart/pull/81) Don't render ConfigMap if `agent.resourceClasses` is unset. This allows you to template your own configmap.
+
 [#71](https://github.com/CircleCI-Public/container-runner-helm-chart/pull/71) Added an option to configure the image name for the orchestrator container, enabling hosting in a private registry or an air-gapped environment on CircleCI server. See the [runner-init repository](https://github.com/circleci/runner-init) for more information.
 
 [#68](https://github.com/CircleCI-Public/container-runner-helm-chart/pull/68) Refactor: Move `logging` container-related resources to their own component subdirectory. This is to work towards a more organized Chart.

templates/configmap.yaml

@@ -1,3 +1,4 @@
+{{- if .Values.agent.resourceClasses }}
 apiVersion: v1
 kind: ConfigMap
 metadata:
@@ -18,3 +19,4 @@ data:
     serviceContainers:
       {{- toYaml .Values.agent.serviceContainers | nindent 6 }}
     {{- end }}
+{{- end }}

tests/configmap_test.yaml

@@ -54,3 +54,9 @@ tests:
                     resources:
                       limits:
                         cpu: 500m
+  - it: should be empty when no resourceClasses are set
+    set:
+      agent.resourceClasses: {}
+    asserts:
+     - hasDocuments:
+        count: 0

values.yaml

@@ -191,6 +191,7 @@ agent:
 
   # -- Resource class settings. The tokens specified here will be used to claim tasks & the tasks
   # will be launched with the configured configs
+  # If you leave this unset you must provide your own configmap named {{ include "container-agent.fullname" . }}
   # Ref: https://circleci.com/docs/container-runner/#resource-class-configuration-custom-pod
   resourceClasses: {}
     # circleci-runner/resourceClass: