Skip to content

values: drop stale worker-temporal mentions in comments#337

Open
cfernhout wants to merge 1 commit into
mainfrom
chiel-values-drop-stale-worker-temporal-comments
Open

values: drop stale worker-temporal mentions in comments#337
cfernhout wants to merge 1 commit into
mainfrom
chiel-values-drop-stale-worker-temporal-comments

Conversation

@cfernhout

Copy link
Copy Markdown
Collaborator

Summary

Two stale worker-temporal references in charts/datafold/values.yaml comments. worker-temporal no longer exists as a releasable worker — it only exists as the shared subchart that every per-queue worker (worker-thunderbolt, worker-io, worker-compute, worker-highmem, worker-storage, worker-storage-high, worker-monitors, worker-catalog, worker-lineage, worker-monitor, worker-singletons, worker-interactive) aliases via Chart.yaml.

line before after
69 # Temporal worker StorageClass ... and PVC storageClassName (worker-temporal). # Temporal worker StorageClass ... and PVC storageClassName.
109 # the server and worker-temporal containers at /datafold/plugins/<fileName>. # the server and all temporal worker containers at /datafold/plugins/<fileName>.

The L109 wording was actively misleading: the custom codec mounts into all temporal worker pods (every alias of the worker-temporal subchart), not just one container named worker-temporal.

Verification

$ grep -n worker-temporal charts/datafold/values.yaml
(no matches)

Test plan

  • No remaining worker-temporal references in values.yaml
  • No semantic change — both edits are comment-only
  • CI checks

Pure docs change, 2 lines edited.

worker-temporal is no longer a releasable worker — it only exists as
the shared subchart that every per-queue worker (worker-thunderbolt,
worker-io, worker-compute, worker-highmem, worker-storage,
worker-storage-high, worker-monitors, worker-catalog, worker-lineage,
worker-monitor, worker-singletons, worker-interactive) aliases via
Chart.yaml.

- L69 parenthetical "(worker-temporal)" no longer adds info; the
  storageClassName name is the only fact worth surfacing.
- L109 "server and worker-temporal containers" was misleading: the
  custom codec mounts into ALL temporal worker pods, not just one
  named 'worker-temporal'.
@github-actions

github-actions Bot commented Jun 1, 2026

Copy link
Copy Markdown

🔍 Kubeconform Validation Results

All cloud provider configurations passed Kubernetes API schema validation!

Cloud Provider Status
AWS ✅ Passed
GCP ✅ Passed
Azure ✅ Passed

The rendered Kubernetes manifests conform to the Kubernetes API specification across all cloud providers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant