多个 Kubernetes 集群同GitLab Core功能的集成

apiVersion: v1
kind: Config
current-context: current-context-name
preferences: {}
clusters:
- cluster:
    Certificate-authority-data: U0FNUExFVEVYVA==
    server: https://10.10.43.1:6443
  name: cluster-name
contexts:
- context:
    cluster: cluster-name
    user: admin-cluster-name
  name: admin-cluster-name
users:
- name: admin-cluster-name
  user:
    client-certificate-data:U0FNUExFVEVYVA==
    Client-key-data: U0FNUExFVEVYVA==

FROM alpine:latest
ARG ENVIRONMENT
ENV KUBECTL_VERSION="1.15.2"
ENV KUBE_ENVIRONMENT=$ENVIRONMENT
RUN apk update && apk add git gettext
RUN apk add --no-cache curl
RUN curl -LO https://storage.googleapis.com/kubernetes-release/release/v${KUBECTL_VERSION}/bin/linux/amd64/kubectl
COPY kube-configs ./kube-configs
RUN chmod +x kubectl
RUN mv kubectl /usr/local/bin/kubectl
RUN mkdir ~/.kube
RUN echo ${KUBE_ENVIRONMENT}
RUN cp /kube-configs/${KUBE_ENVIRONMENT}/config ~/.kube/config
RUN cat ~/.kube/config
RUN kubectl cluster-info

COPY kube-configs ./kube-configs # copy config files to container
RUN chmod +x kubectl # give permission to kubectl
RUN mv kubectl /usr/local/bin/kubectl # move kubectl to bin folder
RUN mkdir ~/.kube  # create folder for configs
RUN echo ${KUBE_ENVIRONMENT} # for check environments (dev,stage, etc.)
RUN cp /kube-configs/${KUBE_ENVIRONMENT}/config ~/.kube/config # to copy configs
RUN cat ~/.kube/config # to check config 
RUN kubectl cluster-info # to check all configs are true or false

# We select docker latest image as a base image for CI/CD steps. Because of our commands based on docker command.
image: docker:latest

# Stages describe the steps of the pipeline. For this project, we need only one step, which is the built step.  
stages:
    - Build

# Before the steps we need to login to our container registry for pull or push docker images. Also, we use GitLabs' docker container registry.
before_script:
  - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY

# This job is for the Development environment. In this job, we pass the ENVIRONMENT ARGUMENT to our Dockerfile. 
# In this job, our ENVIRONMENT is dev. For this reason, our Dockerfile read kubeconfigs for a dev environment.
# After the build completes, we push that image to the GitLab container registry.
# This job works in the build stage and only works for develop branch.
# environment and tags are used for gitlab runner management. information link is https://docs.gitlab.com/runner/register/
Build for Dev:
  stage: Build
  only:
    - develop
  environment:
    name: build
  tags:
    - build
  script:
    - docker build --build-arg ENVIRONMENT=dev -t $CI_REGISTRY_IMAGE:dev .
    - docker push $CI_REGISTRY_IMAGE:dev

# Same as Build for Dev Step
Build for Stage:
  stage: Build
  only:
    - develop
  environment:
    name: build
  tags:
    - build
  script:
    - docker build --build-arg ENVIRONMENT=stage -t $CI_REGISTRY_IMAGE:stage .
    - docker push $CI_REGISTRY_IMAGE:stage

stages:
    - Build
    - Analysis
    - Test
    - Deployment # Adding a new stage

Deploy To Dev:
  stage: Deployment
  image: registry.example.com:5005/base/docker-kubectl:dev
  allow_failure: false
  only:
    - develop
  dependencies:
    - SonarQube
  tags:
    - build
  script:
    - cd kubernetes/
    - /bin/sh deploy.sh dev $CI_PROJECT_NAME $CI_COMMIT_SHORT_SHA

Deploy To Stage:
  stage: Deployment
  image: registry.example.com:5005/base/docker-kubectl:stage
  allow_failure: false
  only:
    - develop
  dependencies:
    - SonarQube
  tags:
    - build
  script:
    - cd kubernetes/
    - /bin/sh deploy.sh stage $CI_PROJECT_NAME $CI_COMMIT_SHORT_SHA

#!/usr/bin/env bash
export ENVIRONMENT=${1}
export APP_NAME=${2}
export SHORT_SHA=${3}
for f in ${ENVIRONMENT}_*.yaml
do
 envsubst <$f> "$(basename "gen_"$f)"
done
 kubectl apply -f gen_${ENVIRONMENT}_service.yaml
 kubectl apply --validate=false -f gen_${ENVIRONMENT}_deployment.yaml
 rm gen_*.yaml