skaffold dev fails if multiple instances use the same port number in different namespaces

[zhlangsas]

Expected behavior

In v0.24.0, multiple instances of skaffold dev should work (worked fine in v0.23.0) when different services in different namespaces have the same port number

Actual behavior

First instance of skaffold dev starts fine, but subsequence deployments using skaffold dev in a different namespace using the same port number fails with FATA[0000] creating runner: creating runner: initializing skaffold event handler: creating status server: creating listener: listen tcp :<port number>: bind: address already in use

Information

• Skaffold version: v0.24.0
• Operating system: macOS 10.14.2
• Contents of first skaffold.yaml:

apiVersion: skaffold/v1beta6
kind: Config
build:
  tagPolicy:
    sha256: {}
  artifacts:
  - image: service1 
deploy:
  helm:
    releases:
    - name: service1 
      chartPath: .chart
      namespace: service1
      wait: true
      valuesFiles:
      - .chart/values-local-dev.yaml
      values:
        imageName: service1

• Contents of second skaffold.yaml:

apiVersion: skaffold/v1beta6
kind: Config
build:
  tagPolicy:
    sha256: {}
  artifacts:
  - image: service12
deploy:
  helm:
    releases:
    - name: service2
      chartPath: .chart
      namespace: service2
      wait: true
      valuesFiles:
      - .chart/values-local-dev.yaml
      values:
        imageName: service2

Steps to reproduce the behavior

1. skaffold dev with first service
2. skaffold dev with second service sharing same port number but different namespace

[nkubala]

hey @zhlangsas, this is fixed with #1752. this will be released with v0.25.0 this week, but in the meantime if you need a workaround you can build from HEAD or downgrade to v0.23.0.