Fix container-name and container-image env var counter if container is excluded via annotation #3007
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Issue
Currently the initContainer of an injected Pod fails, if there is a second container in the list of containers, which is excluded and in-front of the monitored container, in the list of containers.
How can this be tested?
Deploy Operator -> cloudNativeFullStack -> create a sample pod with 2 containers -> exclude the first container in the list of containers from monitoring via annotation on Dynakube
container.inject.dynatrace.com/<container name to exclude>: "false"
(important, it has to be the first one)