Link Search Menu Expand Document

JobDeployment controller

E2E Tests Tests Lint

Working on a controller to manage Job objects

flowchart TD; Deployment -- "manages (through ReplicaSets)" --> Pod; JobDeployment -- manages --> Job;

Problem / Why

  • If you change a batch/v1 Job, tools like Helm fail to apply due to immutable fields.
  • I kinda wish there was a parent object like Deployment to recreate Job objects on changes (similar to how Deployments recreate Pods)
  • Of course, the better solution is often to not use Job objects at all
    • But sometimes with legacy code in your org this might not be an option, so it’d still be nice to have a better way to deploy them

kubebuilder rocks 😎

  • Scaffolds the basics so you can focus on your reconciliation logic

Click where you wanna go
mindmap root((Sean's site)) :::link:/#here-is-my-site Awesome lists 😎 :::link:/awesome-lists/ Awesome tools :::link:/awesome-lists/tools.html Useless websites :::link:/awesome-lists/useless.html Dev stories :::link:/dev-stories/ Metrics exporter :::link:/dev-stories/metrics-exporter.html Pulumi contribution :::link:/dev-stories/pulumi-contribution.html Projects :::link:/projects/ Flake utils :::link:/projects/flake-utils.html Gcloud fzf :::link:/projects/gcloud-fzf.html Job controller :::link:/projects/job-controller.html K3d :::link:/projects/k3d.html This site :::link:/projects/this-site.html Yaml resume :::link:/projects/yaml-resume.html Resume :::link:/resume.html

gimme that fun lil site map