diff --git a/_docs/administration/user-settings.md b/_docs/administration/user-settings.md index 2c33c6aa..b5bb2439 100644 --- a/_docs/administration/user-settings.md +++ b/_docs/administration/user-settings.md @@ -13,12 +13,19 @@ As a user in Codefresh, you can manage your account by authorizing access to you * Authorize Git providers The Git personal token is a user-specific access token, required to authenticate Git-based actions from Codefresh clients, per provisioned runtime. - The authorization method depends on the Git provider and on what authorization has been set up by ypur adin. + + The authorization method depends on the Git provider and on what authorization has been set up by your account admin. + + If your admin has set up authentication with OAuth2, you can authorize access using OAuth2. Or, you can always generate a personal access token from your Git provider and then add the same to Codefresh to authorize access. > If you have access to more than one runtime, you can use the same token for multiple runtimes. - You must however authorize access individually for each runtime. + You must however authorize access individually for each runtime. + +{::nomarkdown} +
+{:/} ### Enable access for Codefresh support Enable Codefresh support personnel to access your user account. Access to your account is useful for visibility during troubleshooting. @@ -40,87 +47,137 @@ You can disable this security setting at any time. max-width="50%" %} -### Authorize Git access with OAuth or personal access tokens -Authorize Git access with OAuth2 if your account admin has set up Codefresh as an OAuth application, or alternatively through personal access tokens from your Git provider. -* For OAuth2: The adminstrator pre-configures the permissions and expiry date. Once you supply your credentials for authorization, you are automatically directed to the Git Personal Tokens page. - -#### Generate personal access token for GitHub - -#### Authorize access for Bitbucket -Bitbucket requires your Bitbucket account name and a personal access token to authorize access. - -**Generate personal access token** - -1. Log in to your Bitbucket Cloud or Server account. -1. Select **Manage account > Account settings > Personal access tokens**. -1. Select these scopes: `repository write`,`Project read`. -1. Copy the personal access token generated as you will need it to authorize access. - -**How to** -1. In the Codefresh UI, go to [User Settings](https://g.codefresh.io/2.0/user-settings){:target="\_blank"}. -1. Select the runtime, and then select one of the following: - * To add a token, select **Add Token**. - * To update an existing token by replacing it with a new token, select **Update Token**. -1. From the **Select Git provider** drop-down, select **Bitbucket**. -1. In the **Bitbucket username field**, enter the username of your Bitbucket account. -1. In the **Bitbucket Personal Access Token** field, paste the token you generated. - - +{::nomarkdown} +
+{:/} +### Authorize Git access in Codefresh +Authorize Git access with OAuth2 if your account admin has set up Codefresh as an OAuth application, or alternatively through personal access tokens from your Git provider. +>Notes: + For OAuth2: The adminstrator pre-configures the permissions and expiry date. Once you supply your credentials for authorization, you are automatically directed to the Git Personal Tokens page. -{:start="6"} -1. Click **Add Token**. - In the Git Personal Access Tokens list, you can see that the new token is assigned to the runtime. +**Before you begin** -#### Authorize access for GitHub -**Before you begin** Make sure you have: * For Bitbucket only, your Bitbucket account username -* If needed, a _personal access token_ with the required scopes: - * [GitHub]({{site.baseurl}}/docs/reference/git-tokens/#github-tokens) - * [GitLab]({{site.baseurl}}/docs/reference/git-tokens/#gitlab-tokens) - * [Bitbucket]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-tokens) +* If needed, a _personal access token_ from your Git provider with the required scopes: + * [GitHub]({{site.baseurl}}/#generate-github-personal-access-tokens) + * [GitLab]({{site.baseurl}}/#generate-gitlab-personal-access-tokens) + * [Bitbucket]({{site.baseurl}}/#generate-bitbucket-personal-access-tokens) **How to** 1. In the Codefresh UI, go to [User Settings](https://g.codefresh.io/2.0/user-settings){:target="\_blank"}. -1. Select the runtime, and then select one of the following: +1. Select the runtime, and then do one of the following: * To add a token, select **Add Token**. * To update an existing token by replacing it with a new token, select **Update Token**. -1. For OAuth2: +1. For **OAuth2**: > If the application is not registered, the button is disabled. Contact your admin for help. * Click **Authorize Access to GitHub**. * Enter your credentials, and select **Sign In**. * Complete the verification if required, as when two-factor authentication is configured, for example. -{:start="4"} -1. For Git personal access tokens: + + For **Git personal access tokens**: * Expand **Advanced authorization options**. - - * In the **Git Personal Access Token** field, paste the token you generated. + * For Bitbucket, enter your **Bitbucket username**. + * In the **Personal Access Token** field, paste the token you generated. {:start="5"} -1. Click **Add Token**. +1. Click **Add Token**. In the Git Personal Access Tokens list, you can see that the new token is assigned to the runtime. +{::nomarkdown} +
+{:/} + +#### Generate GitHub personal access tokens - +1. Log in to your GitHub or GitHub Enterprise account. +1. Select **Settings > Developer Settings > Personal Access Tokens > Tokens (classic)**. +1. Define the following: + * Token name + * Expiration date + * Select scope: `repo` + {% include + image.html + lightbox="true" + file="/images/administration/user-settings/github-pat-scopes.png" + url="/images/administration/user-settings/github-pat-scopes.png" + alt="GitHub personal access token scopes" + caption="GitHub personal access token scopes" + max-width="50%" + %} -{::nomarkdown} -
+{:start="4"} +1. Copy the personal access token generated as you will need it to authorize access. + +{::nomarkdown} +
{:/} +#### Generate GitLab personal access tokens - +1. Log in to your GitLab Cloud or Server account. +1. Select **User settings > Access tokens**. +1. Define the following: + * Token name + * Expiration date + * Select these scopes: `read_api', 'read_user`, `read_repository` + {% include + image.html + lightbox="true" + file="/images/administration/user-settings/gitlab-pat-scopes.png" + url="/images/administration/user-settings/gitlab-pat-scopes.png" + alt="GitLab personal access token scopes" + caption="GitLab personal access token scopes" + max-width="50%" + %} + +{:start="4"} +1. Copy the personal access token generated as you will need it to authorize access. - + +{::nomarkdown} +
+{:/} + +#### Generate Bitbucket personal access tokens + + +1. Log in to your Bitbucket Cloud or Server account. +1. Select **Personal Settings > App passwords**. +1. Define the **Label**. + Select these scopes: + * **Permissions**: `Read` + * **Workspace membership**: `Read` + * **Webhooks**: `Read and write` + * **Repositories**: `Write`, `Admin` + + {% include + image.html + lightbox="true" + file="/images/administration/user-settings/bitbucket-pat-scopes.png" + url="/images/administration/user-settings/bitbucket-pat-scopes.png" + alt="Bitbucket personal access token scopes" + caption="Bitbucket personal access token scopes" + max-width="50%" + %} + +{:start="4"} +1. Copy the personal access token generated as you will need it to authorize access. + +{::nomarkdown} +
+{:/} + ### Related articles [Git tokens in Codefresh]({{site.baseurl}}/docs/reference/git-tokens/) \ No newline at end of file diff --git a/_docs/getting-started/architecture.md b/_docs/getting-started/architecture.md index 4be3ec47..77db5411 100644 --- a/_docs/getting-started/architecture.md +++ b/_docs/getting-started/architecture.md @@ -98,19 +98,6 @@ The App-Proxy performs write and state-change operations:
{:/} -#### Request Routing Service -The Request Routing Service is installed on the same cluster as the Codefresh Runtime in the customer environment. -It receives requests from the Ingress Controller, and forwards the request URLs to the Application Proxy, and webhooks directly to the Event Sources. - - -> Important: - The Request Routing Service is available from runtime version 0.0.543 and higher. - Older runtime versions are not affected as there is complete backward compatibility, and the Ingress Controller continues to route incoming requests. - -{::nomarkdown} -
-{:/} - #### Argo Project The Argo Project includes: @@ -161,11 +148,6 @@ See [Ingress controller]({{site.baseurl}}/docs/runtime/requirements/#ingress-con
{:/} - - - - - #### Managed clusters Managed clusters are external clusters registered to a provisioned hosted or hybrid runtime(s). diff --git a/_docs/runtime/hosted-runtime.md b/_docs/runtime/hosted-runtime.md index 730003b2..0a08ba3b 100644 --- a/_docs/runtime/hosted-runtime.md +++ b/_docs/runtime/hosted-runtime.md @@ -10,7 +10,6 @@ toc: true If you have Codefresh's Hosted GitOps, set up your hosted environment, and you are all ready to leverage extensive CD Ops capabilities. Read about [Hosted GitOps]({{site.baseurl}}/docs/incubation/intro-hosted-runtime/). - ### Where to start with Hosted GitOps If you have not provisioned a hosted runtime, Codefresh presents you with the setup instructions in the **Home** dashboard. @@ -119,7 +118,7 @@ max-width="70%" * [Download the CLI]({{site.baseurl}}/docs/clients/csdp-cli/). 1. Uninstall the failed hosted runtime: - `cf runtime uninstall hosted-codefresh --force` + `cf runtime uninstall codefresh-hosted --force` where: `hosted-codefresh` is the name of your hosted runtime, automatically assigned by Codefresh. 1. In the Codefresh UI, return to Codefresh [Home](https://g.codefresh.io/2.0/?time=LAST_7_DAYS){:target="\_blank"}. @@ -127,9 +126,11 @@ max-width="70%" ### 2. Connect Git provider -Connect your hosted runtime to a Git provider for Codefresh to create the required Git repos. First authorize access to your Git provider through an OAuth token, and then select the Git organizations or accounts in which to create the required Git repos. +Connect your hosted runtime to a Git provider for Codefresh to create the required Git repos. First authorize access to your Git provider through an OAuth token, and then select the Git organizations or accounts in which to create the required Git repos. + >Only authorized organizations are displayed in the list. To authorize organizations for the Codefresh application in GitHub, see [Authorize organizations/projects]({{site.baseurl}}/docs/administration/hosted-authorize-orgs/). + {% include image.html lightbox="true" @@ -140,17 +141,11 @@ caption="Step 2: Connect to Git provider" max-width="80%" %} -You can connect your hosted runtime to any of these Git providers: -* GitHub (the default) -* Bitbucket Cloud - - ->If the hosted runtime is the first runtime you are provisioning for your account, the Git provider you connect to is used for any hybrid runtimes you provision for the same account. This is because of the configuration repo that is created and shared by runtimes in the same account. Once you authorize access, Codefresh creates two Git repositories, one to store the runtime configuration settings, and the other to store the runtime's application settings: * Shared runtime configuration repo - The shared runtime configuration repo is a centralized Git repository that stores configuration settings for the hosted runtime. Additional runtimes provisioned for the account point to this repo to retrieve and reuse the configuration. + The shared runtime configuration repo is a centralized Git repository that stores configuration settings for the hosted runtime. Additional runtimes provisioned for the account can point to this repo to retrieve and reuse the configuration. Read about [Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/). * Git Source application repo diff --git a/_docs/runtime/installation-options.md b/_docs/runtime/installation-options.md index 51121e75..c4d9a334 100644 --- a/_docs/runtime/installation-options.md +++ b/_docs/runtime/installation-options.md @@ -50,16 +50,13 @@ Codefresh Runtime creates three repositories in your organization's Git provider * Codefresh runtime installation repository * Codefresh Git Sources -* Codefresh shared configuration repository +* Codefresh shared configuration repository. It does so for two types of entities: - + By default, the ingress controller directs all requests and events to the Codefresh Application Proxy. When internal and an external ingress hosts are configured, the ingress comtroller directs webhook events to the relevant Event Source and then to Argo Events (not via the Codefresh Application Proxy). ### Hosted vs.Hybrid environments diff --git a/_docs/runtime/installation.md b/_docs/runtime/installation.md index 4a9fa815..c25b7d84 100644 --- a/_docs/runtime/installation.md +++ b/_docs/runtime/installation.md @@ -5,30 +5,19 @@ group: runtime toc: true --- -If you have a hybrid environment, you can provision one or more hybrid runtimes in your Codefresh account. +If you have a hybrid environment, you can provision one or more hybrid runtimes in your Codefresh account. The hybrid runtime comprises Argo CD components and Codefresh-specific components. The Argo CD components are derived from a fork of the Argo ecosystem, and do not correspond to the open-source versions available. > If you have Hosted GitOps, to provision a hosted runtime, see [Provision a hosted runtime]({{site.baseurl}}/docs/runtime/hosted-runtime/#1-provision-hosted-runtime) in [Set up a hosted (Hosted GitOps) environment]({{site.baseurl}}/docs/runtime/hosted-runtime/). -**Git providers and runtimes** -Your Codefresh account is always linked to a specific Git provider. This is the Git provider you select on installing the first runtime - hybrid or hosted - in your Codefresh account. All the hybrid runtimes in the same account use the same Git provider. -If Bitbucker Server is your Git provider, you must also select the specific server instance to associate with the runtime. - ->To change the Git provider for your Codefresh account after installation, contact Codefresh support. - - -**Hybrid runtime** - The hybrid runtime comprises Argo CD components and Codefresh-specific components. The Argo CD components are derived from a fork of the Argo ecosystem, and do not correspond to the open-source versions available. - There are two parts to installing a hybrid runtime: 1. Installing the Codefresh CLI 2. Installing the hybrid runtime from the CLI, either through the CLI wizard or via silent installation through the installation flags. The hybrid runtime is installed in a specific namespace on your cluster. You can install more runtimes on different clusters in your deployment. - Every hybrid runtime installation makes commits to three Git repos: - * Runtime install repo: The installation repo that manages the hybrid runtime itself with Argo CD. If the repo URL does not exist, it is automatically created during runtime installation. - * Git Source repo: Created automatically during runtime installation. The repo where you store manifests for pipelines and applications. See [Git Sources]({{site.baseurl}}/docs/runtime/git-sources). - * Shared configuration repo: Created for the first runtime in a user account. The repo stores configuration manifests for account-level resources and is shared with other runtimes in the same account. See [Shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration). + Every hybrid runtime installation makes commits to two Git repos: + * Runtime install repo: The installation repo that manages the hybrid runtime itself with Argo CD. If the repo URL does not exist, runtime creates it automatically. + * Git Source repo: Created automatically during runtime installation. The repo where you store manifests to run CodefreshCodefresh pipelines. See also [Codefresh architecture]({{site.baseurl}}/docs/getting-started/architecture). @@ -41,8 +30,7 @@ This section describes the required and optional flags to install a hybrid runti For documentation purposes, the flags are grouped into: * Runtime flags, relating to runtime, cluster, and namespace requirements * Ingress controller flags, relating to ingress controller requirements -* Git provider flags, relating to Git provider requirements -* Git repository, user and token flags, relating to generic and provider-specific requirements for Git repos +* Git repository flags, relating to Git provider requirements {::nomarkdown}
@@ -69,7 +57,7 @@ The cluster defined as the default for `kubectl`. If you have more than one Kube * CLI wizard: Select the Kube context from the list displayed. * Silent install: Explicitly specify the Kube context with the `--context` flag. -**Shared configuration repository** +**Shared configuration repository** The Git repository per runtime account with shared configuration manifests. * CLI wizard and Silent install: Add the `--shared-config-repo` flag and define the path to the shared repo. @@ -77,32 +65,8 @@ The Git repository per runtime account with shared configuration manifests.
{:/} - - - #### Ingress controller flags - **Skip ingress** Required, if you are using an unsupported ingress controller. For unsupported ingress controllers, bypass installing ingress resources with the `--skip-ingress` flag. @@ -138,238 +102,45 @@ For both CLI wizard and Silent install: * For existing installations, commit changes to the installation repository by modifying the `app-proxy ingress` and `.yaml` See [(Optional) Internal ingress host configuration for existing hybrid runtimes](#optional-internal-ingress-host-configuration-for-existing-hybrid-runtimes). -{::nomarkdown} -
-{:/} - - - -#### Git provider and repo flags -The Git provider defined for the runtime. - ->Because Codefresh creates a [shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration) for the runtimes in your account, the Git provider defined for the first runtime you install in your account is used for all the other runtimes in the same account. - -You can define any of the following Git providers: -* GitHub: - * [GitHub](#github) (the default Git provider) - * [GitHub Enterprise](#github-enterprise) -* GitLab: - * [GitLab Cloud](#gitlab-cloud) - * [GitLab Server](#gitlab-server) -* Bitbucket: - * [Bitbucket Cloud](#bitbucket-cloud) - * [Bitbucket Server](#bitbucket-server) - -{::nomarkdown} -
-{:/} - - - -##### GitHub -GitHub is the default Git provider for hybrid runtimes. Being the default provider, for both the CLI wizard and Silent install, you need to provide only the repository URL and the Git runtime token. - -> For the required scopes, see [GitHub and GitHub Enterprise runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#github-and-github-enterprise-runtime-token-scopes). - -`--repo --git-token ` - -where: -* `--repo ` (required), is the `HTTPS` clone URL of the Git repository for the runtime installation, including the `.git` suffix. Copy the clone URL from your GitHub website (see [Cloning with HTTPS URLs](https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls){:target="\_blank"}). - If the repo doesn't exist, copy an existing clone URL and change the name of the repo. Codefresh creates the repository during runtime installation. - - Repo URL format: - `https://github.com//reponame>.git[/subdirectory][?ref=branch]` - where: - * `/` is your username or organization name, followed by the name of the repo, identical to the HTTPS clone URL. For example, `https://github.com/nr-codefresh/codefresh.io.git`. - * `[/subdirectory]` (optional) is the path to a subdirectory within the repo. When omitted, the runtime is installed in the root of the repository. For example, `/runtimes/defs`. - * `[?ref=branch]` (optional) is the `ref` queryParam to select a specific branch. When omitted, the runtime is installed in the default branch. For example, `codefresh-prod`. - - Example: - `https://github.com/nr-codefresh/codefresh.io.git/runtimes/defs?ref=codefresh-prod` -* `--git-token ` (required), is the Git token authenticating access to the runtime installation repository (see [Git runtime tokens]({{site.baseurl}}/docs/docs/reference/git-tokens/#git-runtime-tokens)). - -{::nomarkdown} -
-{:/} - -##### GitHub Enterprise - -> For the required scopes, see [GitHub and GitHub Enterprise runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#github-and-github-enterprise-runtime-token-scopes). - - -`--enable-git-providers --provider github --repo --git-token ` - -where: -* `--enable-git-providers` (required), indicates that you are not using the default Git provider for the runtime. -* `--provider github` (required), defines GitHub Enterprise as the Git provider for the runtime and the account. -* `--repo ` (required), is the `HTTPS` clone URL of the Git repository for the runtime installation, including the `.git` suffix. Copy the clone URL for HTTPS from your GitHub Enterprise website (see [Cloning with HTTPS URLs](https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls){:target="\_blank"}). - If the repo doesn't exist, copy an existing clone URL and change the name of the repo. Codefresh creates the repository during runtime installation. - Repo URL format: - - `https://ghe-trial.devops.cf-cd.com//.git[/subdirectory][?ref=branch]` - where: - * `/` is your username or organization name, followed by the name of the repo. For example, `codefresh-io/codefresh.io.git`. - * `[/subdirectory]` (optional) is the path to a subdirectory within the repo. When omitted, the runtime is installed in the root of the repository. For example, `/runtimes/defs`. - * `[?ref=branch]` (optional) is the `ref` queryParam to select a specific branch. When omitted, the runtime is installed in the default branch. For example, `codefresh-prod`. - - Example: - `https://ghe-trial.devops.cf-cd.com/codefresh-io/codefresh.io.git/runtimes/defs?ref=codefresh-prod` -* `--git-token ` (required), is the Git token authenticating access to the runtime installation repository (see [Git runtime tokens]({{site.baseurl}}/docs/docs/reference/git-tokens/#git-runtime-tokens)). - - -{::nomarkdown} -
-{:/} - -##### GitLab Cloud -> For the required scopes, see [GitLab Cloud and GitLab Server runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#gitlab-cloud-and-gitlab-server-runtime-token-scopes). - - -`--enable-git-providers --provider gitlab --repo --git-token ` - -where: -* `--enable-git-providers`(required), indicates that you are not using the default Git provider for the runtime. -* `--provider gitlab` (required), defines GitLab Cloud as the Git provider for the runtime and the account. -* `--repo ` (required), is the `HTTPS` clone URL of the Git project for the runtime installation, including the `.git` suffix. Copy the clone URL for HTTPS from your GitLab website. - If the repo doesn't exist, copy an existing clone URL and change the name of the repo. Codefresh creates the repository during runtime installation. - - > Important: You must create the group with access to the project prior to the installation. - - Repo URL format: - - `https://gitlab.com//.git[/subdirectory][?ref=branch]` - where: - * `` is either your username, or if your project is within a group, the front-slash separated path to the project. For example, `nr-codefresh` (owner), or `parent-group/child-group` (group hierarchy) - * `` is the name of the project. For example, `codefresh`. - * `[/subdirectory]` (optional) is the path to a subdirectory within the repo. When omitted, the runtime is installed in the root of the repository. For example, `/runtimes/defs`. - * `[?ref=branch]` (optional) is the `ref` queryParam to select a specific branch. When omitted, the runtime is installed in the default branch. For example, `codefresh-prod`. - - Examples: - `https://gitlab.com/nr-codefresh/codefresh.git/runtimes/defs?ref=codefresh-prod` (owner) - - `https://gitlab.com/parent-group/child-group/codefresh.git/runtimes/defs?ref=codefresh-prod` (group hierarchy) - -* `--git-token ` (required), is the Git token authenticating access to the runtime installation repository (see [Git runtime tokens]({{site.baseurl}}/docs/docs/reference/git-tokens/#git-runtime-tokens)). - {::nomarkdown}
{:/} +#### Git repository flags +**Repository URLs** +The GitHub repository to house the installation definitions. -##### GitLab Server - -> For the required scopes, see [GitLab Cloud and GitLab Server runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#gitlab-cloud-and-gitlab-server-runtime-token-scopes). - -`--enable-git-providers --provider gitlab --repo --git-token ` +* CLI wizard: If the repo doesn't exist, Codefresh creates it during runtime installation. +* Silent install: Required. Add the `--repo` flag. -where: -* `--enable-git-providers` (required), indicates that you are not using the default Git provider for the runtime. -* `--provider gitlab` (required), defines GitLab Server as the Git provider for the runtime and the account. -* `--repo ` (required), is the `HTTPS` clone URL of the Git repository for the runtime installation, including the `.git` suffix. - If the project doesn't exist, copy an existing clone URL and change the name of the project. Codefresh creates the project during runtime installation. - - > Important: You must create the group with access to the project prior to the installation. - - Repo URL format: - `https://gitlab-onprem.devops.cf-cd.com//.git[/subdirectory][?ref=branch]` - where: - * `` is your username, or if the project is within a group or groups, the name of the group. For example, `nr-codefresh` (owner), or `parent-group/child-group` (group hierarchy) - * `` is the name of the project. For example, `codefresh`. - * `[/subdirectory]` (optional) is the path to a subdirectory within the repo. When omitted, the runtime is installed in the root of the repository. For example, `/runtimes/defs`. - * `[?ref=branch]` (optional) is the `ref` queryParam to select a specific branch. When omitted, the runtime is installed in the default branch. For example, `codefresh-prod`. - - Examples: - `https://gitlab-onprem.devops.cf-cd.com/nr-codefresh/codefresh.git/runtimes/defs?ref=codefresh-prod` (owner) - - `https://gitlab-onprem.devops.cf-cd.com/parent-group/child-group/codefresh.git/runtimes/defs?ref=codefresh-prod` (group hierarchy) - -* `--git-token ` (required), is the Git token authenticating access to the runtime installation repository (see [Git runtime tokens]({{site.baseurl}}/docs/docs/reference/git-tokens/#git-runtime-tokens)). - - -{::nomarkdown} -
-{:/} - -##### Bitbucket Cloud -> For the required scopes, see [Bitbucket Cloud and Bitbucket Server runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-cloud-and-bitbucket-server-runtime-token-scopes). - - -`--enable-git-providers --provider bitbucket --repo --git-user --git-token ` - -where: -* `--enable-git-providers` (required), indicates that you are not using the default Git provider for the runtime. -* `--provider gitlab` (required), defines Bitbucket Cloud as the Git provider for the runtime and the account. -* `--repo ` (required), is the `HTTPS` clone URL of the Git repository for the runtime installation, including the `.git` suffix. - If the project doesn't exist, copy an existing clone URL and change the name of the project. Codefresh creates the project during runtime installation. - >Important: Remove the username, including @ from the copied URL. - - Repo URL format: - - `https://bitbucket.org.git[/subdirectory][?ref=branch]` - where: - * `` is your workspace ID. For example, `nr-codefresh`. - * `` is the name of the repository. For example, `codefresh`. - * `[/subdirectory]` (optional) is the path to a subdirectory within the repo. When omitted, the runtime is installed in the root of the repository. For example, `/runtimes/defs`. - * `[?ref=branch]` (optional) is the `ref` queryParam to select a specific branch. When omitted, the runtime is installed in the default branch. For example, `codefresh-prod`. - - Example: - `https://bitbucket.org/nr-codefresh/codefresh.git/runtimes/defs?ref=codefresh-prod` -* `--git-user ` (required), is your username for the Bitbucket Cloud account. -* `--git-token ` (required), is the Git token authenticating access to the runtime installation repository (see [Git runtime tokens]({{site.baseurl}}/docs/docs/reference/git-tokens/#git-runtime-tokens)). +**Git runtime token** +Required. +The Git token authenticating access to the GitHub installation repository. +* Silent install: Add the `--git-token` flag. {::nomarkdown}
{:/} -##### Bitbucket Server - -> For the required scopes, see [Bitbucket Cloud and Bitbucket Server runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-cloud-and-bitbucket-server-runtime-token-scopes). - - -`--enable-git-providers --provider bitbucket-server --repo --git-user --git-token ` - -where: -* `--enable-git-providers` (required), indicates that you are not using the default Git provider for the runtime. -* `--provider gitlab` (required), defines Bitbucket Cloud as the Git provider for the runtime and the account. -* `--repo ` (required), is the `HTTPS` clone URL of the Git repository for the runtime installation, including the `.git` suffix. - If the project doesn't exist, copy an existing clone URL and change the name of the project. Codefresh then creates the project during runtime installation. - >Important: Remove the username, including @ from the copied URL. - - Repo URL format: - - `https://bitbucket-server-8.2.devops.cf-cd.com:7990/scm//.git[/subdirectory][?ref=branch]` - where: - * `` is your username or organization name. For example, `codefresh-io.`. - * `` is the name of the repo. For example, `codefresh`. - * `[/subdirectory]` (optional) is the path to a subdirectory within the repo. When omitted, the runtime is installed in the root of the repository. For example, `/runtimes/defs`. - * `[?ref=branch]` (optional) is the `ref` queryParam to select a specific branch. When omitted, the runtime is installed in the default branch. For example, `codefresh-prod`. - - Example: - `https://bitbucket-server-8.2.devops.cf-cd.com:7990/scm/codefresh-io/codefresh.git/runtimes/defs?ref=codefresh-prod` -* `--git-user ` (required), is your username for the Bitbucket Server account. -* `--git-token ` (required), is the Git token authenticating access to the runtime installation repository (see [Git runtime tokens]({{site.baseurl}}/docs/docs/reference/git-tokens/#git-runtime-tokens)). - -{::nomarkdown} -

-{:/} - #### Codefresh resource flags **Codefresh demo resources** Optional. Install demo pipelines to use as a starting point to create your own pipelines. We recommend installing the demo resources as these are used in our quick start tutorials. -* Silent install: Add the `--demo-resources` flag, and define its value as `true` (default), or `false`. For example, `--demo-resources=true` +* Silent install: Add the `--demo-resources` flag. By default, set to `true`. **Insecure flag** For _on-premises installations_, if the Ingress controller does not have a valid SSL certificate, to continue with the installation, add the `--insecure` flag to the installation command. {::nomarkdown} -

+
+{:/} +{::nomarkdown} +
{:/} - ### Install the Codefresh CLI @@ -380,11 +151,10 @@ If you are not sure which OS to select for `curl`, simply select one, and Codefr

{:/} -### Install the hybrid runtime +### Install the hybrid runtime **Before you begin** * Make sure you meet the [minimum requirements]({{site.baseurl}}/docs/runtime/requirements/#minimum-requirements) for runtime installation -* Make sure you have [runtime token with the required scopes from your Git provdier]({{site.baseurl}}/docs/reference/git-tokens) * [Download or upgrade to the latest version of the CLI]({{site.baseurl}}/docs/clients/csdp-cli/#upgrade-codefresh-cli) * Review [Hybrid runtime installation flags](#hybrid-runtime-installation-flags) * Make sure your ingress controller is configured correctly: @@ -426,13 +196,15 @@ If you are not sure which OS to select for `curl`, simply select one, and Codefr ### Hybrid runtime components -**Git repositories** +**Git repositories** + * Runtime install repository: The installation repo contains three folders: apps, bootstrap and projects, to manage the runtime itself with Argo CD. * Git source repository: Created with the name `[repo_name]_git-source`. This repo stores manifests for pipelines with sources, events, workflow templates. See [Add Git Sources to runtimes]({{site.baseurl}}/docs/runtime/git-sources/). * Shared configuration repository: Stores configuration and resource manifests that can be shared across runtimes, such as integration resources. See [Shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration/) **Argo CD components** + * Project, comprising an Argo CD AppProject and an ApplicationSet * Installations of the following applications in the project: * Argo CD @@ -441,8 +213,10 @@ If you are not sure which OS to select for `curl`, simply select one, and Codefr * Argo Rollouts **Codefresh-specific components** + * Codefresh Applications in the Argo CD AppProject: - * App-proxy facilitating behind-firewall access to Source entity that references the`[repo_name]_git-source` + * App-proxy facilitating behind-firewall access to Git + * Git Source entity that references the`[repo_name]_git-source` Once the hybrid runtime is successfully installed, it is provisioned on the Kubernetes cluster, and displayed in the **Runtimes** page. @@ -450,8 +224,8 @@ Once the hybrid runtime is successfully installed, it is provisioned on the Kube
{:/} - ### (Optional) Internal ingress host configuration for existing hybrid runtimes + If you already have provisioned hybrid runtimes, to use an internal ingress host for app-proxy communication and an external ingress host to handle webhooks, change the specs for the `Ingress` and `Runtime` resources in the runtime installation repository. Use the examples as guidelines. `/apps/app-proxy/overlays//ingress.yaml`: change `host` diff --git a/_docs/runtime/requirements.md b/_docs/runtime/requirements.md index d62a895e..d5767f75 100644 --- a/_docs/runtime/requirements.md +++ b/_docs/runtime/requirements.md @@ -21,12 +21,12 @@ The requirements listed are the **_minimum_** requirements to provision **_hybri {: .table .table-bordered .table-hover} | Item | Requirement | | -------------- | -------------- | -|Kubernetes cluster | Server version 1.21.0 and higher, without Argo Project components. {::nomarkdown}
Tip: To check the server version, run:
kubectl version --short.{:/}| +|Kubernetes cluster | Server version 1.18 and higher, without Argo Project components. {::nomarkdown}
Tip: To check the server version, run:
kubectl version --short.{:/}| | Ingress controller| Configured on Kubernetes cluster and exposed from the cluster. {::nomarkdown}
Supported and tested ingress controllers include:
  • Ambassador
    • {:/}(see [Ambassador ingress configuration](#ambassador-ingress-configuration)){::nomarkdown}
  • AWS ALB (Application Load Balancer)
    • {:/} (see [AWS ALB ingress configuration](#aws-alb-ingress-configuration)){::nomarkdown}
  • Istio
    • {:/} (see [Istio ingress configuration](#istio-ingress-configuration)){::nomarkdown}
  • NGINX Enterprise (nginx.org/ingress-controller)
    • {:/} (see [NGINX Enterprise ingress configuration](#nginx-enterprise-ingress-configuration)){::nomarkdown}
  • NGINX Community (k8s.io/ingress-nginx)
    • {:/} (see [NGINX Community ingress configuration](#nginx-community-version-ingress-configuration)){::nomarkdown}
  • Trafik
    • {:/}(see [Traefik ingress configuration](#traefik-ingress-configuration))| |Node requirements| {::nomarkdown}
    • Memory: 5000 MB
    • CPU: 2
    {:/}| |Cluster permissions | Cluster admin permissions | -|Git providers |{::nomarkdown}
    • GitHub
    • GitHub Enterprise
    • GitLab Cloud
    • GitLab Server
    • Bitbucket Cloud
    • Bitbucket Server
    {:/}| -|Git access tokens | {::nomarkdown}Git runtime token:
    • Valid expiration date
    • Scopes:
      • GitHub and GitHub Enterprise: repo, admin-repo.hook
      • GitLab Cloud and GitLab Server: api, read_repository
      • Bitbucket Cloud and Bitbucket Server: Project admin, Project read, Repository read
      {:/}| +|Git providers |{::nomarkdown}
      • GitHub
      {:/}| +|Git access tokens | {::nomarkdown}Runtime Git token:
      • Valid expiration date
      • Scopes: repo and admin-repo.hook
      Personal access Git token:
      • Valid expiration date
      • Scopes: repo
    {:/}| - -**On-demand sync for individual application resources** -Sync is a context menu option available for all resources that track sync status. You can sync individual resources as needed or when out-of-sync without synchronizing or refreshing the application. - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-oct-22-sync-context-menu.png" - url="/images/whats-new/rel-notes-oct-22-sync-context-menu.png" - alt="Sync option in resource context menu" - caption="Sync option in resource context menu" - max-width="50%" -%} - -**Rollout resource actions** -The context menu for `rollout` resource types have actions to control the rollout. - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-oct22-rollout-context-menu.png" - url="/images/whats-new/rel-notes-oct22-rollout-context-menu.png" - alt="Context menu options for Rollout resource" - caption="Context menu options for Rollout resource" - max-width="50%" -%} - -{::nomarkdown} -
    -{:/} - -#### Other enhancements - -**Git Sources as Application Type filter** -The list of filters for Application Type in the Applications dashboard includes the Git Source filter. Filtering by Git Source shows `Git Source Apps` which are applications created by Codefresh that store definitions of Argo Project resources. - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-oct22-app-type-git-source.png" - url="/images/whats-new/rel-notes-oct22-app-type-git-source.png" - alt="Git Source as Application Type filter" - caption="Git Source as Application Type filter" - max-width="40%" -%} - - -**Manifests for Analysis Runs** -Analysis Run now shows the manifest in addition to the run results. - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-oct22-analysis-run-manifest.png" - url="/images/whats-new/rel-notes-oct22-analysis-run-manifest.png" - alt="Manifest for Analysis Run" - caption="Manifest for Analysis Run" - max-width="40%" -%} - -{::nomarkdown} -
    -{:/} - -### Bug fixes - -{::nomarkdown} -
    -{:/} - -**Runtimes** - -* 500: Internal Server Error when adding cluster command to hosted runtime. -* Commit SHA link in Activity Log goes to the Home page instead of to the Commit URL for the Git provider. -* Ingress controller errors for cluster even when `skip-ingress` flag is defined. -* Retry mechanism requests cause delay in Git integration checks. -* For hosted runtimes, Git Source is not displayed though the Connect to Git provider step is marked as complete. -* No option to log out on selecting invalid authentication mode. -* Removing a managed cluster does not display any indication in Codefresh UI. -* Up-to-date runtimes display upgrade indication. - - -{::nomarkdown} -
    -{:/} - -**Applications** -* Applications deleted in Git displayed as errors, or as Missing in Codefresh. -* Tagging/untagging favorite application breaks relationship to parent application. -* Application definitions validation for cluster URL that does not exist shows wrong entity type. -* Incorrect number of replicas for previous image in Applications dashboard. -* Mismatch between information reported for cluster and namespace in Applications dashboard and Images. -* Source link in Timeline tab redirects to incorrect branch. -* Missing Health indication for Argo Rollouts in Codefresh UI. - -{::nomarkdown} -
    -{:/} - -**Delivery Pipelines and workflows** -* 100% CPU consumption for workflows with more than 20 nodes. -* Discard Changes button enabled when there are no changes. - - -## September 2022 - - - -### Features & enhancements -{::nomarkdown} -
    -{:/} - -#### Enriched application header -Every application includes a header that highlights key information and links to key aspects of the application. For example, you can see both the current sync state and the result of the previous sync operation, with links to pull-out panels including additional details. - - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-sep22-app-header.png" - url="/images/whats-new/rel-notes-sep22-app-header.png" - alt="Application header for selected appplication" - caption="Application header for selected appplication" - max-width="80%" -%} - -#### Refresh and hard refresh to manage applications -Just as you can manually synchronize applications directly in Codefresh, you can now perform Refresh and Hard Refresh for applications. -In the Applications dashboard, both options are available in the context menu of each application. On selecting an application, you can see them on the top-right next to the Synchronize button. - - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png" - url="/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png" - alt="Refresh/Hard refresh options for selected application" - caption="Refresh/Hard refresh options for selected application" - max-width="80%" -%} - - - -#### Click resume indefinitely paused rollouts -Argo Rollouts allows you to pause a rollout indefinitely and resume it manually instead of automatically after a fixed duration. Manually resuming a rollout is generally done through the CLI. -Codefresh provides you the option of resuming an indefinitely paused rollout directly from the Applications dashboard in Codefresh, with a single click. - -In the Timelines tab of the selected application, an ongoing rollout that is indefinitely paused displays the pause button. Resuming the rollout is as simple as clicking the pause button. - - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-sep22-resume-pause.png" - url="/images/whats-new/rel-notes-sep22-resume-pause.png" - alt="Resume indefinitley paused rollout" - caption="Resume indefinitley paused rollout" - max-width="60%" -%} - -#### Custom path for application resources -When creating applications, in addition to changing the name of the manifest, you can now also define the path for the manifest within the Git Source. Use the front slash (/) to add subfolders to the path. The resource is created in the Git Source you select, according to the path you defined. - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-sep22-app-yaml-location.png" - url="/images/whats-new/rel-notes-sep22-app-yaml-location.png" - alt="Define location for application YAML" - caption="Define location for application YAML" - max-width="60%" -%} - - - -#### Events tab for applications -In the previous month's release, we added the Events panel displaying successful and events for the application. -For more visibility and easier access, the same Events tab is now displayed with the Current State, Timeline, Services, and Configuration tabs for the selected application. - - -{% include - image.html - lightbox="true" - file="/images/whats-new/rel-notes-sep22-events-tab.png" - url="/images/whats-new/rel-notes-sep22-events-tab.png" - alt="Events tab for application" - caption="Events tab for application" - max-width="60%" -%} - - -### Bug fixes - -{::nomarkdown} -
    -{:/} - -**Runtimes** -* Incorrect status for Hosted runtime when app-proxy is unreachable. -* Git provider not registered for hosted runtimes with Git Sources defined in the shared configuration repo. -* Authentication failure between platform and app proxy. -* Adding cluster to a runtime shows an error even when the cluster is added to the runtime. -* Duplicate dates in Activity Log notifications. -* Argo CD fails to connect to K8s 1.24 clusters. -* After uninstalling a runtime, argo-rollouts and rollout-reporter files remain for managed cluster remain in shared configuration repo. -* Deleted managed cluster shows as Unknown. - -{::nomarkdown} -
    -{:/} - -**Applications** -* Health status does not change to progressing when previously degraded. -* Wrong git source reference -* Git Source applications in the Applications dashboard not reflected in the Runtimes > Git Source tab. -* Switching from YAML to form view after changing fields does not update validations. -* App details drawer crashes when application does not have resources. -* Missing namespace for resources. -* Full Screen does not work in Safari. -* Recreating an application with the same name as that of a deleted application displays incorrect data for rollouts in the Timeline tab. -* In the Timeline tab, data for a new release with long sync duration is assigned to the previous release. - +This month's release is all about quality and usability. ## August 2022 @@ -466,8 +142,6 @@ max-width="60%" * Test Connection option disabled when integration name is not defined. - - ## July 2022 ### Features & enhancements @@ -772,7 +446,7 @@ By the very nature of its design, the Tree View allows progressive discovery. Vi **Resource filters** -The filters in the List view are available also in the Tree view. These global filters help narrow the scope of the resources displayed, by kind, health status, and sync state. The filters set in either the List or Tree vies are retained when navigating between them. +The filters in the List view are available also in the Tree view. These global filters help narrow the scope of the resources displayed, by kind, health status, and sync state. The filters set in either the List or Tree views are retained when navigating between them. **Resource search and find** @@ -799,7 +473,7 @@ For details, see [Current State Tree view]({{site.baseurl}}/docs/deployment/appl In addition to installing Argo Rollouts in your cluster, visualize Argo Rollout history and progress directly in the Applications (deployment) dashboard. Visualize rollouts from multiple clusters and runtimes in a single centralized location through the Deployment tab. **Rollout progress** -Ongoing rollouts show the progress of the rollout in the real time. Completed rollouts show the switch to the new version according to the deployment strategy. +Ongoing rollouts show the progress of the rollout in real time. Completed rollouts show the switch to the new version according to the deployment strategy. {% include image.html @@ -930,7 +604,7 @@ For details, see [Runtime installation flags]({{site.baseurl}}/docs/runtime/inst #### Internal and external ingress hosts Codefresh runtimes support defining two ingress hosts, an internal and an external ingress host, for private and public networks. Previously, runtimes supported a single ingress host for both the app-proxy and webhook ingress resources. Internal and external ingress separation allows you to expose the Codefresh app-proxy service only within your private network, while keeping the webhook ingress unchanged. -* New runtime installations: The `--internal-ingress-host` flag lets you can define an ingress host for communication with the app-proxy. For details, see [Runtime installation flags]({{site.baseurl}}/docs/runtime/installation/#runtime-installation-flags). +* New runtime installations: The `--internal-ingress-host` flag lets you define an ingress host for communication with the app-proxy. For details, see [Runtime installation flags]({{site.baseurl}}/docs/runtime/installation/#runtime-installation-flags). * Existing runtimes: To add an internal ingress host, you need to commit changes to the installation repository by modifying `app-proxy ingress` and `.yaml`. For details, see _Internal ingress host configuration (optional)_ in [Post-installation configuration]({{site.baseurl}}/docs/runtime/installation#post-installation-configuration). diff --git a/images/administration/user-settings/bitbucket-pat-scopes.png b/images/administration/user-settings/bitbucket-pat-scopes.png new file mode 100644 index 00000000..3a81e17a Binary files /dev/null and b/images/administration/user-settings/bitbucket-pat-scopes.png differ diff --git a/images/administration/user-settings/github-pat-scopes.png b/images/administration/user-settings/github-pat-scopes.png new file mode 100644 index 00000000..bd3443fb Binary files /dev/null and b/images/administration/user-settings/github-pat-scopes.png differ diff --git a/images/administration/user-settings/gitlab-pat-scopes.png b/images/administration/user-settings/gitlab-pat-scopes.png new file mode 100644 index 00000000..08911e5d Binary files /dev/null and b/images/administration/user-settings/gitlab-pat-scopes.png differ diff --git a/images/applications/rel-notes-aug22-app-context-menu.png b/images/applications/rel-notes-aug22-app-context-menu.png new file mode 100644 index 00000000..a0d7a769 Binary files /dev/null and b/images/applications/rel-notes-aug22-app-context-menu.png differ diff --git a/images/getting-started/architecture/arch-hybrid.png b/images/getting-started/architecture/arch-hybrid.png index 101a9a67..257d456b 100644 Binary files a/images/getting-started/architecture/arch-hybrid.png and b/images/getting-started/architecture/arch-hybrid.png differ diff --git a/images/whats-new/rel-notes-aug22-app-context-menu.png b/images/whats-new/rel-notes-aug22-app-context-menu.png new file mode 100644 index 00000000..a0d7a769 Binary files /dev/null and b/images/whats-new/rel-notes-aug22-app-context-menu.png differ diff --git a/images/whats-new/rel-notes-aug22-app-validation-errors.png b/images/whats-new/rel-notes-aug22-app-validation-errors.png new file mode 100644 index 00000000..5f425f4f Binary files /dev/null and b/images/whats-new/rel-notes-aug22-app-validation-errors.png differ diff --git a/images/whats-new/rel-notes-aug22-events-tab.png b/images/whats-new/rel-notes-aug22-events-tab.png new file mode 100644 index 00000000..ede641d2 Binary files /dev/null and b/images/whats-new/rel-notes-aug22-events-tab.png differ diff --git a/images/whats-new/rel-notes-aug22-github-cr.png b/images/whats-new/rel-notes-aug22-github-cr.png new file mode 100644 index 00000000..e8297d64 Binary files /dev/null and b/images/whats-new/rel-notes-aug22-github-cr.png differ diff --git a/images/whats-new/rel-notes-aug22-githubactions-cr-param.png b/images/whats-new/rel-notes-aug22-githubactions-cr-param.png new file mode 100644 index 00000000..58878963 Binary files /dev/null and b/images/whats-new/rel-notes-aug22-githubactions-cr-param.png differ diff --git a/images/whats-new/rel-notes-aug22-new-app-nav.png b/images/whats-new/rel-notes-aug22-new-app-nav.png new file mode 100644 index 00000000..268226c2 Binary files /dev/null and b/images/whats-new/rel-notes-aug22-new-app-nav.png differ diff --git a/images/whats-new/rel-notes-aug22-quickview-contextmenu.png b/images/whats-new/rel-notes-aug22-quickview-contextmenu.png new file mode 100644 index 00000000..36b47384 Binary files /dev/null and b/images/whats-new/rel-notes-aug22-quickview-contextmenu.png differ diff --git a/images/whats-new/rel-notes-aug22-quickview-events.png b/images/whats-new/rel-notes-aug22-quickview-events.png new file mode 100644 index 00000000..eca4d98a Binary files /dev/null and b/images/whats-new/rel-notes-aug22-quickview-events.png differ diff --git a/images/whats-new/rel-notes-oct-22-rollout-player.png b/images/whats-new/rel-notes-oct-22-rollout-player.png deleted file mode 100644 index 1e01193c..00000000 Binary files a/images/whats-new/rel-notes-oct-22-rollout-player.png and /dev/null differ diff --git a/images/whats-new/rel-notes-oct-22-sync-context-menu.png b/images/whats-new/rel-notes-oct-22-sync-context-menu.png deleted file mode 100644 index bb1422bd..00000000 Binary files a/images/whats-new/rel-notes-oct-22-sync-context-menu.png and /dev/null differ diff --git a/images/whats-new/rel-notes-oct22-analysis-run-manifest.png b/images/whats-new/rel-notes-oct22-analysis-run-manifest.png deleted file mode 100644 index 5305fb84..00000000 Binary files a/images/whats-new/rel-notes-oct22-analysis-run-manifest.png and /dev/null differ diff --git a/images/whats-new/rel-notes-oct22-app-type-git-source.png b/images/whats-new/rel-notes-oct22-app-type-git-source.png deleted file mode 100644 index 76e68fb2..00000000 Binary files a/images/whats-new/rel-notes-oct22-app-type-git-source.png and /dev/null differ diff --git a/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png b/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png deleted file mode 100644 index c443db56..00000000 Binary files a/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png and /dev/null differ diff --git a/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png b/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png deleted file mode 100644 index 7d303e1d..00000000 Binary files a/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png and /dev/null differ diff --git a/images/whats-new/rel-notes-oct22-rollout-context-menu.png b/images/whats-new/rel-notes-oct22-rollout-context-menu.png deleted file mode 100644 index d7a34f01..00000000 Binary files a/images/whats-new/rel-notes-oct22-rollout-context-menu.png and /dev/null differ