feat: scheduler-k3s renders pvc-backed volumes from storage attachments

Adds a per-entry storage helm chart that owns the PVC and (when host_path is set) the PV, and three triggers for the storage plugin to drive: storage-create installs/upgrades the chart with storage-class existence validation, storage-destroy uninstalls it, storage-status reports the PVC phase. App deployment and cron-job charts now consume storage-app-mounts and reference each PVC by name; the // todo: implement volumes blocks are gone. ProcessVolume gained sub_path, read_only, and persistent_claim fields and the deployment/cron-job templates render them.
This commit is contained in:
Jose Diaz-Gonzalez
2026-04-29 14:49:15 -04:00
parent e1b6bdb1d4
commit cfb7da8ec0
10 changed files with 447 additions and 6 deletions

View File

@@ -117,9 +117,12 @@ type ProcessValues struct {
}
type ProcessVolume struct {
Name string `yaml:"name"`
MountPath string `yaml:"mount_path"`
EmptyDir *ProcessVolumeEmptyDir `yaml:"empty_dir,omitempty"`
Name string `yaml:"name"`
MountPath string `yaml:"mount_path"`
SubPath string `yaml:"sub_path,omitempty"`
ReadOnly bool `yaml:"read_only,omitempty"`
EmptyDir *ProcessVolumeEmptyDir `yaml:"empty_dir,omitempty"`
PersistentClaim *ProcessVolumePersistentClaim `yaml:"persistent_claim,omitempty"`
}
type ProcessVolumeEmptyDir struct {
@@ -127,6 +130,10 @@ type ProcessVolumeEmptyDir struct {
SizeLimit string `yaml:"size_limit"`
}
type ProcessVolumePersistentClaim struct {
ClaimName string `yaml:"claim_name"`
}
type ProcessAnnotations struct {
CertificateAnnotations map[string]string `yaml:"certificate,omitempty"`
CronJobAnnotations map[string]string `yaml:"cronjob,omitempty"`