-title:"Other Registries"

url:"/other-registries"

-title:"Quality Assurance"

-title:"Testing"

url:"/testing"

pages:

-title:"Unit testing"

image: mcr.microsoft.com/azure-cli

commands:

- az vm create --resource-group TutorialResources --name TutorialVM1 --image UbuntuLTS --generate-ssh-keys

environment:

- KUBECONTEXT=my-cluster-name

- KUBERNETES_NAMESPACE=my-namespace

{% endraw %}

{% endhighlight %}

If you want to use*LocalSSD* in GKE:

*Prerequisite:*[GKE cluster with local SSD](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd)

*Install runner using GKE Local SSD:*

If you want to use*GCE Disks*:

*Prerequisite:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get of Google disks

There are 3 options to provide cloud credentials on GCE:

* run venona dind-volume-provisioniner on node with iam role which is allowed to create/delete/get of Google disks

* create Google Service Account with`ComputeEngine.StorageAdmin`, download its key and pass it to venona installed with`--set-file=Storage.GooogleServiceAccount=/path/to/google-service-account.json`

* use[Google Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) to assign iam role to`volume-provisioner-venona` service account

Notice that builds will be running in a single availability zone, so you must specify AvailabilityZone parameters.

Install Runner using GKE Disks:

*`cluster-role.dind-volume-provisioner.re.yaml` Defines all the permission needed for the controller to operate correctly.

*`cluster-role-binding.dind-volume-provisioner.yaml` - Binds the ClusterRole to`service-account.dind-volume-provisioner.re.yaml`.

We are now preparing the next version of Codefresh runner with two major changes:

* Installation happens from the[Codefresh CLI](https://codefresh-io.github.io/cli/) from now on. No need for a separate installer any more

* You can use a single agent to manage multiple installations of the runner (even from other Kubernetes clusters)

First follow the[prerequisites](#prerequisites) and make sure that the version of Codefresh CLI is at least 0.45.0

Then to install the runner on a single cluster with both the runtime and the agent:

You can then follow the instruction for[using the runner](#using-the-codefresh-runner).

It is also possible, for advanced users to install a single agent that can manage multiple runtime environments.

Migrating to the new Codefresh runner version is not happening automatically. You need to initiate the migration yourself using our[migration script](https://github.com/codefresh-io/venona/blob/release-1.0/scripts/migration.sh)

If the environment is not functioning correctly for your own application, make sure that the port exposed by Codefresh in the*Launch settings* is the one that is actually used in your application as an HTTP endpoint.

To find your existing on-demand environments, click*Docker Swarm*`->`*Environments* on the left part of the screen. You will get a list of your active environments. You can see details such as:

To find your existing on-demand environments, click*Compositions*`->`*Running Compositions* on the left part of the screen. You will get a list of your active environments. You can see details such as:

* Which branch is this environment from

* Which Git commit represents this environment

max-width="50%"

%}

A new build will start. Once it is complete your new environment will be created. You can inspect it by clicking in the*Docker Swarm* menu on the left sidebar and then clicking*Environments*.

A new build will start. Once it is complete your new environment will be created. You can inspect it by clicking in the*Compositions* menu on the left sidebar and then clicking*Running Compositions*.

{% include image.html

lightbox="true"

3. Build your service with Codefresh

{:start="4"}

4.Go totheenvironment page

4.Click on*Compositions* ontheleft sidebar and then choose the*Running Compositions* tab.

{% include image.html

lightbox="true"

file="/images/a4054be-Screen_Shot_2017-01-19_at_09.27.53.png"

url="/images/a4054be-Screen_Shot_2017-01-19_at_09.27.53.png"

alt="Screen Shot 2017-01-19 at 09.27.53.png"

max-width="40%"

%}

{:start="5"}

5. Youcan see the new environment on this page

5. Youwill see the new preview environment on this page

There is a limit to the number environments you can run concurrently. That's why it's a good practice to launch the the composition only on certain condition. Usually the most relevant condition is the branch, since you probably want your environment to be updated by you main branch.

Compositions can be launched as part of a unit test step, integration test step or for running an image for manual testing. You can create compositions from scratch or import an existing`docker-compose.yml` file.

From the left sidebarexpand the*Docker Swarm* menu andclick the**Compositions** sub menu. Then click the**ADD COMPOSITION** button.

From the left sidebar clickonthe*Compositions* menu. Then click the**ADD COMPOSITION** button.

{% include

image.html

test environment in your Codefresh account that you can use to inspect your application.

{:start="1"}

1. From the left sidebarexpand the*Docker Swarm* menu andclick the**Compositions** sub menu. Then select a composition.

1. From the left sidebar clickonthe*Compositions* menu. Then select a composition.

{% include

image.html

After you successfully spin up a composition, click the**Environments**view iconin the left pane, to viewthe record for the running environment and all containers for the environment.

After you successfully spin up a composition, click the**Running compositions**tab from the*Compositions* itemin the left pane, to viewa record for the running environment and all containers for the environment.

{% include

image.html