diff --git a/README.md b/README.md index 033d13e7..7ee87ddb 100644 --- a/README.md +++ b/README.md @@ -64,7 +64,7 @@ For now, we advise to install Job-Executor-Service in a separate namespace, and Install `job-executor-service` on a kubernetes cluster where `Keptn` is already installed: ```shell -JES_VERSION="0.2.0" +JES_VERSION="0.2.3" JES_NAMESPACE="keptn-jes" TASK_SUBSCRIPTION="sh.keptn.event.remote-task.triggered" # Add the relevant events here in a comma-separated list diff --git a/docs/INSTALL.md b/docs/INSTALL.md index 00e2375d..45ef70ac 100644 --- a/docs/INSTALL.md +++ b/docs/INSTALL.md @@ -16,7 +16,7 @@ In order to install the *job-executor-service* on the remote execution plane, so **Example installation with token:** ```bash -JES_VERSION= # e.g. 0.2.1 +JES_VERSION= # e.g. 0.2.3 KEPTN_API_PROTOCOL=http # or https KEPTN_API_HOST= # e.g., 1.2.3.4.nip.io @@ -45,10 +45,11 @@ If multiple Keptn installations are present, the `remoteControlPlane.autoDetect. The auto-detection feature can be enabled by setting `remoteControlPlane.autoDetect.enabled` to `true`. ```bash +JES_VERSION= # e.g. 0.2.3 TASK_SUBSCRIPTION=sh.keptn.event.remote-task.triggered helm upgrade --install --create-namespace -n \ - job-executor-service https://github.com/keptn-contrib/job-executor-service/releases/download//job-executor-service-.tgz \ + job-executor-service https://github.com/keptn-contrib/job-executor-service/releases/download/${JES_VERSION}/job-executor-service-${JES_VERSION}.tgz \ --set remoteControlPlane.autoDetect.enabled=true \ --set remoteControlPlane.topicSubscription=${TASK_SUBSCRIPTION} \ --set remoteControlPlane.api.token="" \ @@ -66,7 +67,7 @@ If the oauth authentication mode should be used instead of the token, the follow * `remoteControlPlane.api.oauth.scopes` - The scopes which should be requested by the job executor service ```bash -JES_VERSION= # e.g. 0.2.1 +JES_VERSION= # e.g. 0.2.3 KEPTN_API_PROTOCOL=http # or https KEPTN_API_HOST= # e.g., 1.2.3.4.nip.io