Merge branch '187-new-job-deploy-to-k8s-cluster-without-helm' into latest

templating

Templating

auths

kubeconfig

subfolders

severities

Kustomize

namespace

## Objective

This job will deploy your YAML files to a Kubernetes cluster, the cluster can be linked with Gitlab or provided using a `KUBECONFIG` variable

## How to use it

!!! important

    If you want to deploy multiple YAML files, you need to provide the name of the folder containing the files in the variable `FILES_LOCATION`.

    If also you have subfolders, you need to add `--recursive` in `$KUBECTL_OPTIONS`

1. Make sure that you have a Kubernetes cluster, you have two options:

      1. Use a linked cluster with your Gitlab project, get more info [here](https://docs.gitlab.com/ee/user/project/clusters/){:target="_blank"}

      1. Provide a kubeconfig file through the variable `KUBECONFIG`, check [THIS](https://docs.gitlab.com/ee/ci/variables/#cicd-variable-types){:target="_blank"} guide to see how

1. Add this job URL inside the `include` list of your `.gitlab-ci.yml` file (see the [quick setup](/use-the-hub/#quick-setup)). You can specify [a fixed version](#changelog) instead of `latest`.

    ```yaml

      - remote: 'https://jobs.r2devops.io/latest/kubectl_deploy.yml'

    ```

1. Provide the value of the variable `FILES_LOCATION`, check [**Variables**](#variables)

1. If you need to customize the job (stage, variables, ...) 👉 check the [jobs

   customization](/use-the-hub/#jobs-customization)

1. Well done, your job is ready to work ! 😀

## Job details

* Job name: `kubectl_deploy`

* Docker image:

[`bitnami/kubectl:1.19.11`](https://hub.docker.com/r/bitnami/kubectl)

* Default stage: `deploy`

* When: `manual`, only when running on default branch (`$CI_DEFAULT_BRANCH`).  

  To update this behavior, see [job customization](https://r2devops.io/use-the-hub/#global) to override [`rules`](https://docs.gitlab.com/ee/ci/yaml/#rulesif)

### Variables

!!! important

    If you want to provide a kubeconfig file, please create a file variable named `$KUBECONFIG`, you can do that by passing them as [CI/CD variables](https://docs.gitlab.com/ee/ci/variables/#cicd-variable-types){:target="_blank"} so that your data can stay confidential.

| Name | Description | Default |

| ---- | ----------- | ------- |

| `FILES_LOCATION` | Folder name, if multiple .yaml files; Or file name that contains the manifests | ` ` |

| `KUBECTL_OPTIONS` | Additional options for the command kubectl | ` ` |

!!! info

    Here is an example of what you can put in `FILES_LOCATION` if you have multiple files but not in the same folder  

        ```yaml

        FILES_LOCATION: "myfile1.yaml -f myfile2.yaml -f myfile3.yml"

        ```

name: kubectl_deploy

description: This job will deploy your YAML files to a kubernetes cluster

default_stage: deploy

icon: 🌌

maintainer: moha-s

license: Apache-2.0

images:

  bitnami/kubectl:1.19.11

tools:

labels:

  - GitLab

  - Utilities

  - kubernetes

  - Deploy

 No newline at end of file

# Job from R2Devops hub --> r2devops.io

stages:

  - deploy

kubectl_deploy:

  image: 

    name: bitnami/kubectl:1.19.11

    entrypoint: [""]

  stage: deploy

  variables:

    FILES_LOCATION: ""

    KUBECTL_OPTIONS: ""

  script:

  - kubectl apply -f $FILES_LOCATION $KUBECTL_OPTIONS | tee -a output.log

  environment:

      name: ${CI_COMMIT_REF_SLUG}

  artifacts:

    expose_as: "Kubectl job output"

    paths:

      - output.log

  rules:

    - if: '$CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'

 No newline at end of file

* Initial version

 No newline at end of file