Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"multiple deploy.kubectl.defaultNamespace values set" when depending on multiple configurations with different namespaces #8941

Open
jackwilsdon opened this issue Jul 12, 2023 · 1 comment
Labels
kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases

Comments

@jackwilsdon
Copy link
Contributor

Expected behavior

Depending on two configurations with different namespaces does not produce a warning.

Actual behavior

Depending on two configurations with different namespaces produces the following warning:

WARN[0000] multiple deploy.kubectl.defaultNamespace values set, only last pipeline's value will be used  subtask=-1 task=DevLoop

The manifests are deployed to the correct namespaces, so the warning doesn't seem correct.

Information

  • Skaffold version: v2.6.0
  • Operating system: macOS Ventura 13.4.1
  • Installed via: skaffold.dev
  • Contents of skaffold.yaml:
    apiVersion: skaffold/v4beta5
    kind: Config
    requires:
      - path: project-a/skaffold.yaml
      - path: project-b/skaffold.yaml

Steps to reproduce the behavior

  1. git clone https://github.com/jackwilsdon/skaffold-kubectl-namespace-issue
  2. cd skaffold-kubectl-namespace-issue
  3. skaffold run
@ericzzzzzzz ericzzzzzzz added kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases labels Jul 13, 2023
@AndreasBergmeier6176
Copy link
Contributor

It seems seeing this error message also this means that StatusMonitor does not work properly anymore!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases
Projects
None yet
Development

No branches or pull requests

3 participants