[deckhouse] application batch hook

[ipaqsa]

Description

It is related with it

And this

It provides application batch hook

{"level":"info","logger":"deckhouse-controller.operator.application-loader.batch-hook.executor","msg":"application cleanup","source":"go/pkg/mod/github.com/flant/shell-operator@v1.13.1/pkg/executor/executor.go:322","hook_logger":"hook-controller.batch/cleanup/hook","hook_module":"default.test","hook_name":"test","hook_namespace":"default","hook_source":"usr/src/app/hooks/batch/cleanup/hook.go:40","output":"stdout","proxyJsonLog":true,"time":"2026-01-20T12:34:54Z"}

Why do we need it, and what problem does it solve?

Application hooks need instance namespace and name.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: deckhouse
type: chore
summary: Application batch hook.
impact_level: low