build(deps): bump flame_k8s_backend from 0.5.7 to 0.6.0

[dependabot]

Bumps flame_k8s_backend from 0.5.7 to 0.6.0.

Release notes

Sourced from flame_k8s_backend's releases.

v0.6.0

This release revamps the runner pod manifest configuration. The migration steps depend on the value you are currently passing:

• If you are currently passing a map or a callback to :runner_pod_tpl, you can simply rename the option to :manifest and it should maintain the current behaviour.

• If you are using %FLAMEK8sBackend.RunnerPodTemplate{} with :env and/or :resources fields, you need to convert it into a manifest map.

  manifest = %{
    "spec" => %{
      "containers" => [
        %{
          "env" => [
            %{"name" => "FOO", "value" => "bar"}
          ],
          "resources" => %{
            "requests" => %{"memory" => "256Mi", "cpu" => "100m"},
            "limits" => %{"memory" => "256Mi", "cpu" => "400m"}
          }
        }
      ]
    }
  }
  {FLAME.Pool,
  name: MyApp.SamplePool,
  backend: {FLAMEK8sBackend, manifest: manifest}}

  Note that, by default, using %FLAMEK8sBackend.RunnerPodTemplate{} implied that envs and resources were copied from the parent pod. If you want to maintain that behaviour, you can use a manifest function, as fallows:

    manifest_fun = fn parent_pod_manifest, app_container ->
      %{
        "spec" => %{
          "containers" => [
            %{
              # Copy env vars and resources from the parent container definition.
              # For fields that you don't want to copy, you can specify the desired
              # values here.
              "env" => app_container["env"] || [],
              "envFrom" => app_container["envFrom"] || [],
              "resources" => app_container["resources"] || %{}
            }
          ]
        }
      }
    end
  {FLAME.Pool,
  

... (truncated)

Changelog

Sourced from flame_k8s_backend's changelog.

[0.6.0] - 2026-03-06

This release revamps the runner pod manifest configuration. The migration steps depend on the value you are currently passing:

• If you are currently passing a map or a callback to :runner_pod_tpl, you can simply rename the option to :manifest and it should maintain the current behaviour.

• If you are using %FLAMEK8sBackend.RunnerPodTemplate{} with :env and/or :resources fields, you need to convert it into a manifest map.

  manifest = %{
    "spec" => %{
      "containers" => [
        %{
          "env" => [
            %{"name" => "FOO", "value" => "bar"}
          ],
          "resources" => %{
            "requests" => %{"memory" => "256Mi", "cpu" => "100m"},
            "limits" => %{"memory" => "256Mi", "cpu" => "400m"}
          }
        }
      ]
    }
  }
  {FLAME.Pool,
  name: MyApp.SamplePool,
  backend: {FLAMEK8sBackend, manifest: manifest}}

  Note that, by default, using %FLAMEK8sBackend.RunnerPodTemplate{} implied that envs and resources were copied from the parent pod. If you want to maintain that behaviour, you can use a manifest function, as fallows:

    manifest_fun = fn parent_pod_manifest, app_container ->
      %{
        "spec" => %{
          "containers" => [
            %{
              # Copy env vars and resources from the parent container definition.
              # For fields that you don't want to copy, you can specify the desired
              # values here.
              "env" => app_container["env"] || [],
              "envFrom" => app_container["envFrom"] || [],
              "resources" => app_container["resources"] || %{}
            }
          ]
        }
      }
    end

... (truncated)

Commits

• 74411b9 release v0.6.0
• b1f9b79 Add :manifest and :env backend options, remove runner template struct (#134)
• b0c7e12 Update mruoss/action_elixir_run_tests action to v2.2.0 (#130)
• fd57b3e Update dependency erlang to v28.4 (#132)
• 835b50d Update dependency erlang to v28.3.3 (#129)
• 54e923b Update dependency credo to v1.7.17 (#131)
• 49dc327 Update dependency erlang to v28.3.2 (#128)
• 667d29b Update dependency yaml_elixir to v2.12.1 (#127)
• c0e3ddd Update dependency ex_doc to v0.40.1 (#126)
• 5dc5aec Update dependency credo to v1.7.16 (#125)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)