Implicitly make the first node the bootstrap node to avoid new values

charts/chainlink-cluster/templates/chainlink-node-deployment.yaml

@@ -1,4 +1,4 @@
-{{- range $cfg := .Values.chainlink.nodes }}
+{{- range $index, $cfg := .Values.chainlink.nodes }}
 apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -18,10 +18,10 @@ spec:
         app: {{ $.Release.Name }}
         instance: {{ $cfg.name }}
         release: {{ $.Release.Name }}
-        # Role value should either be: bootstrap or node.
+        # Used for testing. Role value should either be: bootstrap or node.
         # There should only be one "bootstrap" node, the rest should be "node".
-        # This is used for testing.
-        role: {{ $cfg.role }}
+        # Here we set the first node to be bootstrap, the rest to be node.
+        role: {{ if eq $index 0 }}bootstrap{{ else }}node{{ end }}
         {{- range $key, $value := $.Values.labels }}
         {{ $key }}: {{ $value | quote }}
         {{- end }}

charts/chainlink-cluster/values.yaml

@@ -24,7 +24,6 @@ chainlink:
   p2p_port: 6690
   nodes:
     - name: node-1
-      role: bootstrap
       image: "public.ecr.aws/chainlink/chainlink:latest"
       # default resources are 300m/1Gi
       # first node need more resources to build faster inside container
@@ -69,15 +68,10 @@ chainlink:
     # or use overridesToml to override some part of configuration
     #      overridesToml: |
     - name: node-2
-      role: node
     - name: node-3
-      role: node
     - name: node-4
-      role: node
     - name: node-5
-      role: node
     - name: node-6
-      role: node
   resources:
     requests:
       cpu: 350m