diff --git a/k8s-cluster/base/devsite/apps_v1_deployment_devsite.yaml b/k8s-cluster/base/devsite/apps_v1_deployment_devsite.yaml index 2e09ba4..33be441 100644 --- a/k8s-cluster/base/devsite/apps_v1_deployment_devsite.yaml +++ b/k8s-cluster/base/devsite/apps_v1_deployment_devsite.yaml @@ -2,7 +2,7 @@ apiVersion: apps/v1 kind: Deployment metadata: annotations: - app.kubernetes.io/version: 4.2.0 + app.kubernetes.io/version: 4.2.1 generation: 1 labels: app.kubernetes.io/component: devsite @@ -21,7 +21,7 @@ spec: template: metadata: annotations: - app.kubernetes.io/version: 4.2.0 + app.kubernetes.io/version: 4.2.1 creationTimestamp: null labels: app.kubernetes.io/component: devsite diff --git a/k8s-cluster/base/pgbouncer/apps_v1_deployment_pgbouncer.yaml b/k8s-cluster/base/pgbouncer/apps_v1_deployment_pgbouncer.yaml index ddb0860..c9991eb 100644 --- a/k8s-cluster/base/pgbouncer/apps_v1_deployment_pgbouncer.yaml +++ b/k8s-cluster/base/pgbouncer/apps_v1_deployment_pgbouncer.yaml @@ -32,7 +32,7 @@ spec: value: verify-full - name: SERVER_TLS_CA_FILE value: /var/ca-bundle/postgres/postgres-ca.pem - image: us.gcr.io/zenhub-public/pgbouncer:zhe-4.2.0 + image: us.gcr.io/zenhub-public/pgbouncer:zhe-4.2.1 imagePullPolicy: IfNotPresent lifecycle: preStop: diff --git a/k8s-cluster/kustomization.yaml b/k8s-cluster/kustomization.yaml index ca94d93..6f717e0 100644 --- a/k8s-cluster/kustomization.yaml +++ b/k8s-cluster/kustomization.yaml @@ -32,32 +32,32 @@ commonLabels: app.kubernetes.io/managed-by: kustomize commonAnnotations: - app.kubernetes.io/version: 4.2.0 + app.kubernetes.io/version: 4.2.1 # [EDIT] If your cluster does not have access to our public Docker registry, # update the `newName` values with paths to your own private Docker registry. images: - name: kraken-webapp newName: us.gcr.io/zenhub-public/kraken-webapp - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: kraken-extension newName: us.gcr.io/zenhub-public/kraken-extension - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: kraken-zhe-admin newName: us.gcr.io/zenhub-public/kraken-zhe-admin - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: raptor-backend newName: us.gcr.io/zenhub-public/raptor-backend - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: toad-backend newName: us.gcr.io/zenhub-public/toad-backend - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: sanitycheck newName: us.gcr.io/zenhub-public/sanitycheck - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: devsite newName: us.gcr.io/zenhub-public/devsite - newTag: zhe-4.2.0 + newTag: zhe-4.2.1 - name: busybox newName: docker.io/library/busybox newTag: latest diff --git a/k8s-cluster/update/batch_v1_job_data_migration.yaml b/k8s-cluster/update/batch_v1_job_data_migration.yaml index 4021b20..ae326a8 100644 --- a/k8s-cluster/update/batch_v1_job_data_migration.yaml +++ b/k8s-cluster/update/batch_v1_job_data_migration.yaml @@ -389,7 +389,7 @@ spec: secretKeyRef: key: clickhouse_url name: raptor - image: us.gcr.io/zenhub-public/raptor-backend:zhe-4.2.0 + image: us.gcr.io/zenhub-public/raptor-backend:zhe-4.2.1 imagePullPolicy: Always name: data-migration resources: diff --git a/k8s-cluster/update/batch_v1_job_data_migration_previous.yaml b/k8s-cluster/update/batch_v1_job_data_migration_previous.yaml index d345f9b..c552ca9 100644 --- a/k8s-cluster/update/batch_v1_job_data_migration_previous.yaml +++ b/k8s-cluster/update/batch_v1_job_data_migration_previous.yaml @@ -389,7 +389,7 @@ spec: secretKeyRef: key: clickhouse_url name: raptor - image: us.gcr.io/zenhub-public/raptor-backend:zhe-4.2.0 + image: us.gcr.io/zenhub-public/raptor-backend:zhe-4.2.1 imagePullPolicy: Always name: data-migration resources: diff --git a/virtual-machine/README.md b/virtual-machine/README.md index 6c14cc7..a002ad3 100644 --- a/virtual-machine/README.md +++ b/virtual-machine/README.md @@ -430,7 +430,7 @@ If you need to know how to update existing certificates without downtime, see se #### 3.4.1 Zenhub Application TLS -Generate a certificate for your main application domain, like `https://.` +Generate a passwordless certificate for your main application domain, like `https://.` Copy the certificate and key pair to the following path: @@ -438,13 +438,15 @@ Copy the certificate and key pair to the following path: `${ZENHUB_HOME}/configuration/ssl/tls.crt` - certificate +> ⚠️ **NOTE:** The application comes with self-signed certificates set up by default. If you want to provide your own certificates, you can safely replace the self-signed certificates with your own. + > ⚠️ **NOTE:** The certificate and key must be named `tls.crt` and `tls.key` as in the example above. -> ⚠️ **NOTE:** Zenhub will automatically generate a new self-signed certificate if `ssl_self_signed` is set to `true` in the configuration file. Set `ssl_self_signed` to `false` if you want to provide your own self-signed certificates. +> ⚠️ **NOTE:** Zenhub will automatically generate a new self-signed certificate if `ssl_self_signed` is set to `true` in the configuration file. Set `ssl_self_signed` to `false` or leave it unset if you want to provide your own self-signed certificates. #### 3.4.2 Developer Site TLS -Generate a certificate for your developer site domain, like `https://developers-.` +Generate a passwordless certificate for your developer site domain, like `https://developers-.` Copy the certificate and key pair to the following path: @@ -452,6 +454,8 @@ Copy the certificate and key pair to the following path: `${ZENHUB_HOME}/configuration/ssl/developer-site/tls.crt` - certificate +> ⚠️ **NOTE:** The application comes with self-signed certificates set up by default. If you want to provide your own certificates, you can safely replace the self-signed certificates with your own. + > ⚠️ **NOTE:** The certificate and key must be named `tls.crt` and `tls.key` as in the example above. ## 4. Application Deployment @@ -498,7 +502,7 @@ To successfully upgrade, ensure you have sufficient disk space available on your ### 5.2 Preparing to Upgrade -⚠️ **NOTE:** Starting in version 4.2.0, you can now upgrade from two minor versions behind the latest release. For example, if the latest release is 4.2.0, you can upgrade from 4.0.X or 4.1.X. +⚠️ **NOTE:** Starting in version 4.2, you can now upgrade from two minor versions behind the latest release. For example, if the latest release is 4.2.8, you can upgrade from 4.0.X or 4.1.X. 1. Before upgrading, you should always check the release notes for the version you are upgrading to. You can find the release notes for each version in the [releases](https://github.com/ZenHubHQ/zenhub-enterprise/releases) section of this repository. You must ensure you are upgrading to a version that is compatible with your GitHub Enterprise Server version. The release notes list the GitHub Enterprise Server versions that are compatible with each Zenhub Enterprise release. @@ -1057,7 +1061,7 @@ If you wish to remove your log aggregator setup and revert to our default out-of 1. Undo the changes made in section 6.1.3 - Set fluentdconf to be `fluentd.conf` - - Run `kustomize edit set image fluentd=us.gcr.io/zenhub-public/fluentd:zhe-4.2.0` + - Run `kustomize edit set image fluentd=us.gcr.io/zenhub-public/fluentd:zhe-4.2.1` 2. Perform the steps in section 6.1.4 ## 9. Developer Site