chore(module): disabling state tracking for dvcr deployment

[universal-itengineer]

Description

Disabling state tracking for dvcr deployment

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

We need this scheme to work after implementing nelm in deckhouse: deploy a chart with a service, wait until the service is assigned a serviceIP, detect this with a hook, adjust the values, and roll out the chart again.

What is the expected result?

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: module
type: chore
summary: disabling state tracking for dvcr deployment
impact_level: low