Environments on JayeX - Cloud Native CI/CD Built On Kubernetes

Git

Mon, 01 Jan 0001 00:00:00 +0000

Each kubernetes cluster has a git repository so that all the kubernetes resources in all namespaces can be managed by GitOps. Each cluster may also have a separate infrastructure git repository (e.g. for Terraform) to define the cloud resources (buckets, IAM roles, kubernetes cluster, node pools, VPNs, firewalls etc).

So if you use a Multi Cluster Setup you have git repository per cluster to define the kubernetes resources in all the namespaces in that cluster.

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

In your development cluster git repository the jx-requirements.yml file is used to define which are the default environments are used for promotion on your repositories.

The default configuration for environments looks something like this:

apiVersion: core.jenkins-x.io/v4beta1
kind: Requirements
spec:
  ...
  environments:
  - key: dev
  - key: staging
  - key: production

which defaults to meaning that Staging and Production are namespaces (jx-staging and jx-production) in the local cluster. Staging will use Auto promotion and Production will use Manual (more on that later).

Previews

Mon, 01 Jan 0001 00:00:00 +0000

JayeX lets you spin up Preview Environments for your Pull Requests so you can get fast feedback before changes are merged to the main branch. This gives you faster feedback for your changes before they are merged and released and allows you to avoid having human approval inside your release pipeline to speed up delivery of changes merged to master.

When the Preview Environment is up and running JayeX will comment on your Pull Request with a link so in one click your team members can try out the preview!