Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Updated hosted runtime#938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 4 commits intomasterfromgitops-runtime-updates
Mar 5, 2024
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
69 changes: 18 additions & 51 deletions_docs/installation/gitops/hosted-runtime.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -47,8 +47,8 @@ max-width="80%"



##Before you begin
* Set up integrations with the Git provider for the Hosted GitOps Runtime
##Prerequisites
* Set up integrations with the Git provider for the Hosted GitOps Runtime:
* GitHub
* Bitbucket Cloud
* Gerrit
Expand DownExpand Up@@ -78,33 +78,28 @@ max-width="80%"
* In the Codefresh UI, click the **Settings** icon on the toolbar.
* From Runtimes in the sidebar, select [**GitOps Runtimes**](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}, and click **+ Add Runtime**.
* Select **Hosted Runtime** and click **Add**.
{{site.data.callout.callout_tip}}
**TIP**
An account can be provisioned with a single Hosted GitOps Runtime. If you have already provisioned a Hosted GitOps Runtime for your account, the Hosted GitOps Runtime option is disabled.
{{site.data.callout.end}}
* Continue from _step 3_.


{:start="3"}
1. When complete, to view the components for the Hosted GitOps Runtime, click **View Runtime**.
You are directed to the Runtime Components tab.
1. Optional. When complete, click **View Runtime**.
* You can see that there are two steps to complete setup for the Hosted GitOps Runtime.
* The Runtime Components tab is empty as the Runtime components are hosted and managed by Codefresh.
When Argo Rollouts is deployed on target clusters, the Runtime Components tab displays rollout reporters whose manifests are stored in the customer's Shared Configuration Repository created for the Runtime (described in Step 2).
* The Git Sources and the Managed Clusters tabs are also empty as they will be set up in the next steps.


{% include
image.html
lightbox="true"
file="/images/runtime/hosted-runtime-components.png"
url="/images/runtime/hosted-runtime-components.png"
alt="Runtime components forHosted GitOps Runtime"
caption="Runtime components forHosted GitOps Runtime"
alt="Hosted GitOps Runtime after installation"
caption="Hosted GitOps Runtime after installation"
max-width="70%"
%}

{{site.data.callout.callout_tip}}
**TIP**
You can see that there are two steps to complete Hosted GitOps setup.
The Git Sources and the Managed Clusters are empty as they will be set up in the next steps.
{{site.data.callout.end}}

If you navigate to **Runtimes > List View**, you can identify the Hosted GitOps Runtime through the Type column (Hosted),the Cluster/Namespace column (Codefresh), and the Module column (CD Ops).
If you navigate to **Runtimes > List View**, you can identify the Hosted GitOps Runtime through the Type column (Hosted) andthe Cluster/Namespace column (Codefresh).

{% include
image.html
Expand All@@ -116,35 +111,7 @@ caption="Hosted GitOps Runtime in List view"
max-width="70%"
%}

<!--- Ask Idan if to keep this:
### Troubleshoot failed Hosted GitOps Runtime installation
Your Hosted GitOps Runtime may fail to install with an error as in the image below. We are closely moinitoring the Hosted GitOps Runtime installation process and activley working to prevent and iron out all installation errors. Follow the instructions to uninstall and reinstall the Hosted GitOps Runtime.

{% include
image.html
lightbox="true"
file="/images/runtime/hosted-runtime-error.png"
url="/images/runtime/hosted-runtime-error.png"
alt="Hosted runtime installation error"
caption="Hosted runtime installation error"
max-width="70%"
%}


1. Download the CLI
* If you have installed the Codefresh CLI already, make sure you have the latest version:
`cf version`
To compare with the latest version from Codefresh, [click here](https://github.com/codefresh-io/cli-v2/releases){:target="\_blank"}.
* [Download the CLI]({{site.baseurl}}/docs/clients/csdp-cli/).

1. Uninstall the failed Hosted GitOps Runtime:
`cf runtime uninstall codefresh-hosted --force`
where:
`hosted-codefresh` is the name of your Hosted GitOps 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"}.
1. Refresh the page and start with [Step 1: Install Hosted GitOps Runtime](#step-1-install-hosted-gitops-runtime).

-->
## Step 2: Connect Git provider
Connect your Hosted GitOps Runtime to a Git provider for Codefresh to create the required Git repos.

Expand All@@ -166,7 +133,7 @@ max-width="80%"
%}


Once you authorize access, Codefresh creates two Git repositories, one to store the configuration settings for GitOps Runtimes, and the other to store the Runtime's application settings:
Once you authorize access, Codefresh creates two Git repositories, one to store the configuration settings for GitOps Runtimes, and the other to store the Runtime's application settings as a Git Source:
* Shared Configuration Repository
The Shared Configuration Repository is a centralized Git repository that stores configuration settings for the Hosted GitOps Runtime. Additional Hybrid runtimes provisioned for the account can point to this repo to retrieve and reuse the configuration.
Read about [Shared Configuration Repositories]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).
Expand All@@ -176,11 +143,11 @@ Once you authorize access, Codefresh creates two Git repositories, one to store
Codefresh creates a Git Source application repo for every Hosted GitOps Runtime.
Read about [Git sources]({{site.baseurl}}/docs/installation/gitops/git-sources/).

### Before you begin
##### Before you begin
Make sure you have the credentials for the Git provider handy


### How to
##### How to

1. From the list, select the Git provider.
1. Enter the credentials for the selected Git provider:
Expand DownExpand Up@@ -240,7 +207,7 @@ max-width="70%"
1. Optional. To see your tokens, click **View Tokens**.

If you return to the Runtimes page and select the Git Source tab, you will now see the Git Source that Codefresh created.
The Sync State may be Unknown for a few moments untilit is synced to the Codefresh cluster.
The Sync State may be Unknown for a few moments untilthe Git Source is synced to the Codefresh cluster.

{% include
image.html
Expand DownExpand Up@@ -269,10 +236,10 @@ caption="Step 3: Connect a K8s cluster for Hosted GitOps Runtime"
max-width="70%"
%}

**Before you begin**
#####Before you begin
* Make sure your cluster has internet access

**How to**
#####How to
1. Click **Connect**.
1. In the Add Managed Cluster panel, copy the command `cf cluster add`, and run it in the terminal.
1. When prompted to select the `kube-context`, select from the list of available clusters as defined in `kubeconfig`.
Expand Down
Binary file modifiedimages/runtime/hosted-runtime-components.png
View file
Open in desktop
Loading
Sorry, something went wrong.Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
[8]ページ先頭
©2009-2025 Movatter.jp