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

Commit96bf99b

Browse files
committed
Add optional runtime config to byoa
Added optional runtime configuration for private registries and custom repo certificates to install with existing argo
1 parent1db7098 commit96bf99b

File tree

2 files changed

+67
-36
lines changed

2 files changed

+67
-36
lines changed

‎_docs/installation/gitops/hybrid-gitops-helm-installation.md‎

Lines changed: 32 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,9 @@ helm upgrade --install <helm-release-name> \
122122
After installation, you can:
123123
* Continue with the Configuration & Management steps in the installation wizard. See[Configure GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/#configure-gitops-runtime).
124124
* View the installed Runtime in the Runtimes page, and complete the configuration at a later time.
125+
* Depending on your setup, complete the post-installation configuration:
126+
* For private registries, you need to[override specific image values](#image-overrides-for-private-registries).
127+
* If your Git servers are on-premises,[add custom repository certificates](#custom-repository-certificates).
125128

126129
#####View installed Runtime
127130
After installation, go to**GitOps Runtimes > List View**:
@@ -144,13 +147,36 @@ After installation, go to **GitOps Runtimes > List View**:
144147
%}
145148

146149

150+
##Optional GitOps Runtime configuration
147151

148-
{% if page.collection != site.gitops_collection %}
149-
###(Optional) Post-installation configuration
150-
After completing the installation, you may need to perform additional configuration depending on your setup.
151-
* For private registries, you need to[override specific image values](#image-overrides-for-private-registries).
152-
* If your Git servers are on-premises,[add custom repository certificates](#custom-repository-certificates).
153-
{% endif %}
152+
###Image overrides for private registries
153+
If you use private registries, you must override specific image values for the different subcharts and container images.
154+
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.
155+
For more details, see[ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.
156+
157+
###Custom repository certificates
158+
159+
Repository certificates are required to authenticate users to on-premises Git servers.
160+
161+
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"}.
162+
163+
{% highlight yaml %}
164+
global:
165+
codefresh:
166+
tls:
167+
caCerts:
168+
# optional - use an existing secret that contains the cert
169+
# secretKeyRef:
170+
# name: my-certificate-secret
171+
# key: ca-bundle.crt
172+
# or create "codefresh-tls-certs" secret
173+
secret:
174+
create: true
175+
content: |
176+
-----BEGIN CERTIFICATE-----
177+
...
178+
-----END CERTIFICATE-----
179+
{% endhighlight yaml %}
154180

155181

156182

@@ -202,39 +228,9 @@ By default, the GitOps Runtime can deploy to the cluster it is installed on. You
202228

203229

204230

205-
{% if page.collection != site.gitops_collection %}
206-
##Optional GitOps Runtime configuration
207-
208-
###Image overrides for private registries
209-
If you use private registries, you must override specific image values for the different subcharts and container images.
210-
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.
211-
For more details, see[ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.
212231

213-
###Custom repository certificates
214232

215-
Repository certificates are required to authenticate users to on-premises Git servers.
216233

217-
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"}.
218-
219-
{% highlight yaml %}
220-
global:
221-
codefresh:
222-
tls:
223-
caCerts:
224-
# optional - use an existing secret that contains the cert
225-
# secretKeyRef:
226-
# name: my-certificate-secret
227-
# key: ca-bundle.crt
228-
# or create "codefresh-tls-certs" secret
229-
secret:
230-
create: true
231-
content: |
232-
-----BEGIN CERTIFICATE-----
233-
...
234-
-----END CERTIFICATE-----
235-
{% endhighlight yaml %}
236-
237-
{% endif %}
238234

239235

240236
##Related articles

‎_docs/installation/gitops/runtime-install-with-existing-argo-cd.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,9 @@ After installation, you can:
139139
* Continue with the Configuration & Management steps in the installation wizard. See[Configure GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/#configure-gitops-runtime).
140140
OR
141141
* View the installed Runtime in the Runtimes page, and complete the configuration at a later time.
142+
* Depending on your setup, complete the post-installation configuration:
143+
* For private registries, you need to[override specific image values](#image-overrides-for-private-registries).
144+
* If your Git servers are on-premises,[add custom repository certificates](#custom-repository-certificates).
142145

143146
#####View installed Runtime
144147
After installation, go to**GitOps Runtimes > List View**:
@@ -161,6 +164,38 @@ After installation, go to **GitOps Runtimes > List View**:
161164
%}
162165

163166

167+
##Optional GitOps Runtime configuration
168+
169+
###Image overrides for private registries
170+
If you use private registries, you must override specific image values for the different subcharts and container images.
171+
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.
172+
For more details, see[ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.
173+
174+
###Custom repository certificates
175+
176+
Repository certificates are required to authenticate users to on-premises Git servers.
177+
178+
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"}.
179+
180+
{% highlight yaml %}
181+
global:
182+
codefresh:
183+
tls:
184+
caCerts:
185+
# optional - use an existing secret that contains the cert
186+
# secretKeyRef:
187+
# name: my-certificate-secret
188+
# key: ca-bundle.crt
189+
# or create "codefresh-tls-certs" secret
190+
secret:
191+
create: true
192+
content: |
193+
-----BEGIN CERTIFICATE-----
194+
...
195+
-----END CERTIFICATE-----
196+
{% endhighlight yaml %}
197+
198+
164199
##Install GitOps Runtime via Terraform
165200

166201
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"}.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp