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

General

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

What is the directory layout?

To understand the directory layout see this document and the file reference

How do I add an Environment

With v3 everything is done via GitOps - so if in doubt the answer is to modify git.

You can create new environments by adding to the environments: section of jx-requirements.yml

How do I change promotion for my app?

Usually when you import a repository or create a quickstart they inherit the default environments for promotion. It is common to share the same environments across all of your microservices.

Charts and resources

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

How do I add a chart?

To add a new chart add to the helmfiles/mynamespace/helmfile.yaml file follow the add chart guide.

How do I customise an App in an Environment?

We use helmfile to configure helm charts whether its in the dev, staging or production environment and whether you are using multiple clusters.

See how to customise a chart

For a given namespace called ns there is a folder in the cluster git repository at:

Registries

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

How do I use a custom container registry?

What container registry is used by default depends on the which cloud provider you use. There are some things to consider when migrating from container registry to artifact registry in Google GCP.

To allow a pipeline to be able to push to a container registry you can add this secret…

kubectl create secret generic container-registry-auth  \
  --from-literal=url=myserver.com \
  --from-literal=username=myuser \
  --from-literal=password=mypwd

This will then take effect the next time a commit merges on your cluster git repository e.g. next time you upgrade your cluster.

Repositories

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

How do I customise a Scheduler?

The .jx/gitops/source-config.yaml file in your dev cluster git repository lets you configure the name of the scheduler to use for all repositories, for a group of repositories or for an individual repository.

The schedular name is then resolved to be either a file versionStream/schedulers/$name.yaml or schedulers/$name.yaml.

So if you want to create your own Scheduler you could copy the default in-repo based scheduler versionStream/schedulers/in-repo.yaml to schedulers/myname.yaml and then modify it to suit - then associate myname with whatever repositories you wish to use this scheduler for.

Secrets

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

How do I add a new Secret?

See how to add a new Secret

How do I edit a secret?

Secrets are stored in external secret storage like Vault or your cloud providers secret store.

So you can edit them in the underlying secret store directly (e.g. with your cloud providers CLI or the vault CLI).

Or you can use jx secret edit command to do this for you.

The interactive mode is a nice way to find the secret and property you want to edit, then edit…

Vault

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

After an upgrade the boot job is waiting for vault in jx-vault

In the alpha we used to install vault via the helmfile/secret-infra/helmfile.yaml file and install vault into the secret-infra namespace.

A production installation of vault requires cloud resources such as a key ring, crypto key and bucket.

So to make it easier to manage vault properly with cloud resources and to simplify the operation of JayeX (so that the secret store can be used on an empty cluster before we boot anything in the boot process) we have moved the installation of vault into terraform. (e.g for GKE)

Ingress

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

How do I configure the ingress domain in Dev, Staging or Production?

With the new helm 3 based boot every environment uses boot - so there is a single way to configure anything whether its in the dev, staging or production environment and whether or not you are using multiple clusters.

You can override the domain name for use in all apps within an environment by modifying the jx-requirements.yml in the git repository for the dev, staging or production environment.