@@ -391,6 +391,72 @@ Here is a list of the resources that are created during a Runner installation:
391391* ` cluster-role.dind-volume-provisioner.re.yaml ` Defines all the permission needed for the controller to operate correctly.
392392* ` cluster-role-binding.dind-volume-provisioner.yaml ` - Binds the ClusterRole to` service-account.dind-volume-provisioner.re.yaml ` .
393393
394+ ##Codefresh Runner Preview release
395+
396+ We are now preparing the next version of Codefresh runner with two major changes:
397+
398+ * Installation happens from the[ Codefresh CLI] ( https://codefresh-io.github.io/cli/ ) from now on. No need for a separate installer any more
399+ * You can use a single agent to manage multiple installations of the runner (even from other Kubernetes clusters)
400+
401+ > This release is only offered as a preview. Do not use it for production deployments yet.
402+
403+ First follow the[ prerequisites] ( #prerequisites ) and make sure that the version of Codefresh CLI is at least 0.45.0
404+
405+ Then to install the runner on a single cluster with both the runtime and the agent:
406+
407+ ```
408+ kubectl create namespace codefresh
409+ codefresh install agent --kube-namespace codefresh --install-runtime
410+
411+ ```
412+
413+ You can then follow the instruction for[ using the runner] ( #using-the-codefresh-runner ) .
414+
415+ ###Installing multiple runtimes with a single agent
416+
417+ It is also possible, for advanced users to install a single agent that can manage multiple runtime environments.
418+
419+ > NOTE: Please make sure that the cluster where the agent is installed has network access to the other clusters of the runtimes
420+
421+ ```
422+ # 1. Create namespace for the agent:
423+ kubectl create namespace codefresh-agent
424+
425+ # 2. Install the agent on the namespace ( give your agent a unique name as $NAME):
426+ # Note down the token and use it in the second command.
427+ codefresh create agent $NAME
428+ codefresh install agent --token $TOKEN --kube-namespace codefresh-agent
429+ codefresh get agents
430+
431+ # 3. Create namespace for the first runtime:
432+ kubectl create namespace codefresh-runtime-1
433+
434+ # 4. Install the first runtime on the namespace
435+ # 5. the runtime name is printed
436+ codefresh install runtime --kube-namespace codefresh-runtime-1
437+
438+ # 6. Attach the first runtime to agent:
439+ codefresh attach runtime --agent-name $AGENT_NAME --agent-kube-namespace codefresh-agent --runtime-name $RUNTIME_NAME --kube-namespace codefresh-runtime-1
440+
441+ # 7. Restart the venona pod in namespace `codefresh-agent`
442+ kubectl delete pods $VENONA_POD
443+
444+ # 8. Create namespace for the second runtime
445+ kubectl create namespace codefresh-runtime-2
446+
447+ # 9. Install the second runtime on the namespace
448+ codefresh install runtime --kube-namespace codefresh-runtime-2
449+
450+ # 10. Attach the second runtime to agent and restart the Venoa pod automatically
451+ codefresh attach runtime --agent-name $AGENT_NAME --agent-kube-namespace codefresh-agent --runtime-name $RUNTIME_NAME --runtime-kube-namespace codefresh-runtime-1 --restart-agent
452+ ```
453+
454+ ###Migrating to the new Codefresh runner version
455+
456+ 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 )
457+
458+ > This release is only offered as a preview. Do not use it for production deployments yet.
459+
394460
395461
396462##Using the Codefresh Runner