You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
* Continue with the Configuration & Management steps in the installation wizard. See [Configure GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/#configure-gitops-runtime).
* View the installed Runtime in the Runtimes page, and complete the configuration at a later time.
* View the installed Runtime in the Runtimes page.
* Depending on your setup, complete the post-installation configuration:
* For private registries, you need to [override specific image values](#image-overrides-for-private-registries).
* If your Git servers are on-premises, [add custom repository certificates](#custom-repository-certificates).
##### View installed Runtime
After installation, go to **GitOps Runtimes > List View**:
Expand All
@@ -144,13 +147,36 @@ After installation, go to **GitOps Runtimes > List View**:
%}
## Optional GitOps Runtime configuration
{% if page.collection != site.gitops_collection %}
### (Optional) Post-installation configuration
After completing the installation, you may need to perform additional configuration depending on your setup.
* For private registries, you need to [override specific image values](#image-overrides-for-private-registries).
* If your Git servers are on-premises, [add custom repository certificates](#custom-repository-certificates).
{% endif %}
### Image overrides for private registries
If you use private registries, you must override specific image values for the different subcharts and container images.
Our utility helps override image values for GitOps Runtimes by creating `values` files that match the structure of the subcharts, allowing you to easily replace image registries. During chart installation, you can provide these `values` files to override the images, as needed.
For more details, see [ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.
### Custom repository certificates
Repository certificates are required to authenticate users to on-premises Git servers.
If your Git servers are on-premises, add the repository certificates to your Codefresh `values` file, in `.values.argo-cd`. These values are used by the Argo CD that Codefresh deploys. For details on adding repository certificates, see this [section](https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.29.2-cap-CR-18430/charts/argo-cd/values.yaml#LL336C7-L336C7){:target="\_blank"}.
{% highlight yaml %}
global:
codefresh:
tls:
caCerts:
# optional - use an existing secret that contains the cert
Feel free to use a different chart version and a unique name for the Runtime.You can get the values for both the Codefresh API token and account ID from the Codefresh UI as explained in the previous section.
You can get the values for both the Codefresh API token and account ID from the Codefresh UI as explained in the previous section.
The example is valid for the tunnel-based access mode. For ingress-based or service-mesh-based access modes, add the required arguments and values, as described in [GitOps Runtimes with ingress controllers/service meshes]({{site.baseurl}}/docs/installation/gitops/runtime-install-ingress-service-mesh-access-mode/).
Depending on your configuration:
* If you have private registries, you need to override specific image values, and if your Git servers are on-premises, you need to add custom repository certificates. See [Optional GitOps Runtime configuration](#optional-gitops-runtime-configuration) in this article.
* If you installed the GitOps Runtime on a cluster with Argo CD, you can [migrate Community Argo CD Applications](#migrate-argo-cd-applications-to-codefresh-gitops-runtime) to GitOps applications.
Depending on your configuration, if you have private registries, you need to override specific image values, and if your Git servers are on-premises, you need to add custom repository certificates. See [Optional GitOps Runtime configuration](#optional-gitops-runtime-configuration) in this article.
By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add [Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use [Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and [create and deployGitOps applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).
By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add [Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use [Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and [create and deployArgo CD applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).
{% if page.collection != site.gitops_collection %}
## Optional GitOps Runtime configuration
### Image overrides for private registries
If you use private registries, you must override specific image values for the different subcharts and container images.
Our utility helps override image values for GitOps Runtimes by creating `values` files that match the structure of the subcharts, allowing you to easily replace image registries. During chart installation, you can provide these `values` files to override the images, as needed.
For more details, see [ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.
### Custom repository certificates
Repository certificates are required to authenticate users to on-premises Git servers.
If your Git servers are on-premises, add the repository certificates to your Codefresh `values` file, in `.values.argo-cd`. These values are used by the Argo CD that Codefresh deploys. For details on adding repository certificates, see this [section](https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.29.2-cap-CR-18430/charts/argo-cd/values.yaml#LL336C7-L336C7){:target="\_blank"}.
{% highlight yaml %}
global:
codefresh:
tls:
caCerts:
# optional - use an existing secret that contains the cert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
* Continue with the Configuration & Management steps in the installation wizard. See [Configure GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/#configure-gitops-runtime).
OR
* View the installed Runtime in the Runtimes page, and complete the configuration at a later time.
* View the installed Runtime in the Runtimes page.
* Depending on your setup, complete the post-installation configuration:
* For private registries, you need to [override specific image values](#image-overrides-for-private-registries).
* If your Git servers are on-premises, [add custom repository certificates](#custom-repository-certificates).
##### View installed Runtime
After installation, go to **GitOps Runtimes > List View**:
Expand All
@@ -161,6 +163,38 @@ After installation, go to **GitOps Runtimes > List View**:
%}
## Optional GitOps Runtime configuration
### Image overrides for private registries
If you use private registries, you must override specific image values for the different subcharts and container images.
Our utility helps override image values for GitOps Runtimes by creating `values` files that match the structure of the subcharts, allowing you to easily replace image registries. During chart installation, you can provide these `values` files to override the images, as needed.
For more details, see [ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.
### Custom repository certificates
Repository certificates are required to authenticate users to on-premises Git servers.
If your Git servers are on-premises, add the repository certificates to your Codefresh `values` file, in `.values.argo-cd`. These values are used by the Argo CD that Codefresh deploys. For details on adding repository certificates, see this [section](https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.29.2-cap-CR-18430/charts/argo-cd/values.yaml#LL336C7-L336C7){:target="\_blank"}.
{% highlight yaml %}
global:
codefresh:
tls:
caCerts:
# optional - use an existing secret that contains the cert
# secretKeyRef:
# name: my-certificate-secret
# key: ca-bundle.crt
# or create "codefresh-tls-certs" secret
secret:
create: true
content: |
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
{% endhighlight yaml %}
## Install GitOps Runtime via Terraform
You can also use Terraform to install additional GitOps Runtimes with the [Helm provider](https://registry.terraform.io/providers/hashicorp/helm/latest/docs){:target="\_blank"}.
You can get the values for both the Codefresh API token and account ID from the Codefresh UI as explained in the previous section.
The example is valid for the tunnel-based access mode. For ingress-based or service-mesh-based access modes, add the required arguments and values, as described in [GitOps Runtimes with ingress controllers/service meshes]({{site.baseurl}}/docs/installation/gitops/runtime-install-ingress-service-mesh-access-mode/).
Depending on your configuration, if you have private registries, you need to override specific image values, and if your Git servers are on-premises, you need to add custom repository certificates. See [Optional GitOps Runtime configuration](#optional-gitops-runtime-configuration) in this article.
By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add [Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use [Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and [create and deploy Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.