fix(slime): render spec.replicas correctly when Values.replicas is 0

[kb-yusukekimura]

Summary

Fix a bug in the slime chart where Values.replicas: 0 is silently ignored and the Deployment is rendered without spec.replicas, causing Kubernetes to default the replica count to 1.

Root cause

Go template truthiness treats the numeric value 0 as falsy. The condition at templates/deployment.yaml:18 used .Values.replicas directly, so when replicas: 0 was set the and short-circuited to false and the entire replicas: block was skipped during rendering.

-  {{- if and (not .Values.autoscaling.enabled) .Values.replicas }}
+  {{- if and (not .Values.autoscaling.enabled) (ne .Values.replicas nil) }}

The same pattern is already used in php/templates/deployment.yaml:16 (ne .Values.replicaCount nil); this PR aligns slime with that precedent.

Changes

• slime/templates/deployment.yaml: switch the replicas guard to a nil comparison.
• slime/Chart.yaml: bump version from 1.3.1 to 1.3.2 (semver patch / bugfix).

Behavior matrix

Case	Before	After
replicas unset	no spec.replicas	no spec.replicas (unchanged)
replicas: 2	spec.replicas: 2	spec.replicas: 2 (unchanged)
replicas: 0	(bug) no spec.replicas → K8s defaults to 1	spec.replicas: 0
autoscaling.enabled: true + replicas: 2	no spec.replicas (HPA wins)	no spec.replicas (unchanged)
autoscaling.enabled: true + replicas: 0	no spec.replicas (HPA wins)	no spec.replicas (unchanged)

Verification

Test values used for helm template runs:

# /tmp/replicas-zero.yaml
deployment:
  enabled: true
replicas: 0
containers:
  - name: app
    image:
      repository: nginx
      tag: latest

1. Before the fix — bug reproduced (no spec.replicas)

$ helm template -f /tmp/replicas-zero.yaml slime/
...
spec:
  selector:               # <-- replicas line is missing
    matchLabels:
      app.kubernetes.io/name: slime
...

2. After the fix — replicas: 0 is rendered correctly

$ helm template -f /tmp/replicas-zero.yaml slime/
...
spec:
  replicas: 0             # <-- rendered as expected
  selector:
    matchLabels:
      app.kubernetes.io/name: slime
...

3. After the fix — autoscaling.enabled: true + replicas: 0 still omits spec.replicas (HPA wins)

$ helm template -f /tmp/replicas-zero-hpa.yaml slime/
...
spec:
  selector:               # <-- no replicas (HPA owns scaling)
    matchLabels:
      app.kubernetes.io/name: slime
...
---
# Source: slime/templates/hpa.yaml
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
...

4. helm lint --strict passes on all examples

Ran helm lint --strict -f examples/<name>.yaml slime/ against deployment, deployment-hpa, deployment-ingress, cronjob, and cronjob-advanced. All five passed:

==> Linting slime
[INFO] Chart.yaml: icon is recommended
1 chart(s) linted, 0 chart(s) failed

Note: kubeval was not installed locally, so the kubeval portion of make lint is delegated to CI.

Test plan

• helm template renders spec.replicas: 0 when replicas: 0 is set
• helm template omits spec.replicas when autoscaling.enabled: true + replicas: 0
• helm lint --strict passes for all five example values files
• CI runs make lint (kubeval included) successfully

[tasuku43]

LGTM!!