Should skaffold debug be configurable per artifact?

[corneliusweig]

Maybe this is not a real concern. But if somebody has many microservices and wants to debug exactly one, there is currently no way to tell Skaffold that all the other containers should run conventionally.

My concern is that debug requires more resources and makes applications slower. If I already know which part I want to debug, I don't like all other microservices being run in debug mode as well. WDYT?

CC @briandealwis

[briandealwis]

I think it makes sense. Perhaps the command line can be extended to allow specifying the specific artifacts to be debugged.

[nkubala]

we could also mark the artifacts in the skaffold.yaml as debug: false if we know that we don't want to debug them. that might be easier for users than specifying --debug-artifact=gcr.io/debug/container on the CLI, though I don't see any reason why we can't have both.

[corneliusweig]

If debug=true/false is also added in the skaffold.yaml, why not open up a new group such as:

artifacts:
- image: gcr.io/foo/bar
  debug:
    enabled: true
    runtimeType: go

See #2203 for details about runtimeType

[briandealwis]

Right now an artifact can be ignored by adding an annotation to the resource's metadata like the following:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: app
  annotations:
    debug.cloud.google.com/config: "{}"

[briandealwis]

Usecase: running a react serving front-end within Kubernetes https://nirajsonawane.github.io/2020/04/25/Deploy-React-Spring-Boot-MongoDB-Fullstack-application-on-Kubernetes/

The react serving container runs NPM but is not debuggable.

[arikkfir]

Right now an artifact can be ignored by adding an annotation to the resource's metadata like the following:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: app
  annotations:
    debug.cloud.google.com/config: "{}"

Did not work for me on Skaffold v2.4.1 and configuration file at version v4beta5