nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Atlassian/kubectl-run by default runs with --dry-run enabled

Jurgen Heeffer

I'm using atlassian/kubectl-run:3.3.1 and trying to deploy resources in a namespace that doesn't exist yet but is created in the same apply.

The namespace is defined like this:

apiVersion: v1
kind: Namespace
metadata:
  name: namespace-name

Due to the pipe running dry-run by default I'm unable to apply both the namespace resources and the to be deployed resources in a single apply.

Is there a way around this (by disabling the dry-run by default) or am I stuck creating the namespaces and the resources in two separate applys?

Accepted answers

Igor Stoyanov

Hi @Jurgen Heeffer . Thanks for your question. Please provide us your configuration details of how you use the pipe.

Maybe you use the pipe this way:

script:
  - pipe: atlassian/kubectl-run:3.3.1
    variables:
      KUBE_CONFIG: $KUBE_CONFIG
      KUBECTL_COMMAND: 'apply'
      RESOURCE_PATH: 'nginx.yml'
      KUBECTL_ARGS:
        - '--dry-run'

then you should remove '--dry-run' from KUBECTL_ARGS.

Regards, Igor

All comments

Igor Stoyanov

Hi @Jurgen Heeffer . Thanks for your question. Please provide us your configuration details of how you use the pipe.

Maybe you use the pipe this way:

script:
  - pipe: atlassian/kubectl-run:3.3.1
    variables:
      KUBE_CONFIG: $KUBE_CONFIG
      KUBECTL_COMMAND: 'apply'
      RESOURCE_PATH: 'nginx.yml'
      KUBECTL_ARGS:
        - '--dry-run'

then you should remove '--dry-run' from KUBECTL_ARGS.

Regards, Igor

Jurgen Heeffer

Hi @Igor Stoyanov

I'm currently using it like this.

- pipe: atlassian/kubectl-run:3.3.1
  variables:
    KUBE_CONFIG: ${!kube_config}
    KUBECTL_COMMAND: 'apply'
    KUBECTL_APPLY_ARGS: '-k'
    RESOURCE_PATH: '.deploy/overlays/${ENVIRONMENT}/'

I'm not currently specifying dry-run.

With regards,

Jurgen

Igor Stoyanov

@Jurgen Heeffer Thanks for your response. Please provide also your pipeline output.

Regards, Igor

Igor Stoyanov

--dry-run is used in validate spec file by default, and i guess you receive

spec file validation failed error. Our team may think about disable validation with an option available for user, will be this solution ok for you?

Regards, Igor

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

kubernetes