Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package rmt-server-image for 
openSUSE:Factory checked in at 2024-07-08 19:08:56
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rmt-server-image (Old)
 and      /work/SRC/openSUSE:Factory/.rmt-server-image.new.2080 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rmt-server-image"

Mon Jul  8 19:08:56 2024 rev:13 rq:1186122 version:unknown

Changes:
--------
--- /work/SRC/openSUSE:Factory/rmt-server-image/rmt-server-image.changes        
2024-06-19 16:39:12.991012876 +0200
+++ 
/work/SRC/openSUSE:Factory/.rmt-server-image.new.2080/rmt-server-image.changes  
    2024-07-08 19:09:23.085207578 +0200
@@ -1,0 +2,5 @@
+Mon Jul  8 08:57:27 UTC 2024 - Dmitri Popov <dmitri.po...@suse.com>
+
+- README update to include helm chart instructions
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ README.md ++++++
--- /var/tmp/diff_new_pack.jjfLNb/_old  2024-07-08 19:09:24.689266241 +0200
+++ /var/tmp/diff_new_pack.jjfLNb/_new  2024-07-08 19:09:24.717267266 +0200
@@ -8,9 +8,8 @@
 
 ## Overview
 
-To deploy SUSE RMT on top of Kubernetes, each component of the stack is 
deployed in a dedicated container via a
-Helm Chart.
-
+To deploy SUSE RMT on top of Kubernetes, each component of the stack is 
deployed in a dedicated container using a
+Helm chart.
 ### Repository Mirroring Tool (SUSE RMT) server
 
 A containerized version of the SUSE RMT application that can pass its 
configuration via Helm values. Because persistent storage resides on a 
persistent volume, you need to adjust the volume size according to the number 
of repositories you need to mirror.
@@ -34,10 +33,14 @@
 - a running Kubernetes cluster
 - helm command configured to interact with the cluster
 
+The Helm chart can be obtained using the following command:
+
+`helm pull oci://registry.suse.com/suse/rmt-helm`
+
 ## Custom mandatory values
 
 Certain values of the chart do not have any defaults:
-- SCC mirroring credentials (refer to [more 
information](https://documentation.suse.com/sles/15-SP4/html/SLES-all/cha-rmt-mirroring.html#sec-rmt-mirroring-credentials)
 for more information)
+- SCC mirroring credentials (refer to [more 
information](https://documentation.suse.com/sles/html/SLES-all/cha-rmt-mirroring.html#sec-rmt-mirroring-credentials)
 for more information)
 - list of products to mirror
 - list of products not to mirror
 - DNS name used to reach the RMT server
@@ -45,9 +48,10 @@
 
 Before deploying the chart, you must fill a custom values file.
 
-The following example enables ingress with TLS.
-The create-certs.sh can be used to create self-signed certificates and
-add them to Kubernetes as a usable TLS secret.
+The following example enables ingress with TLS. The `create-certs.sh` script
+supplied with the Helm chart can be used
+to create self-signed certificates and add them to Kubernetes as a usable TLS
+secret.
 
 ```
 cat << EOF > myvalues.yaml
@@ -81,10 +85,27 @@
 EOF
 ```
 
+The required values in the custom value file are as follows:
+
+- `app.scc.password` SUSE Customer Center proxy password. The password string 
must be in quotes. If the quote character `"` is part of the string, it has to 
be escaped with `\`.
+- `app.scc.username` SUSE Customer Center proxy user name. The user name 
string must be quotes. If the quote character `"` is part of the string, it has 
to be escaped with `\`.
+- `app.scc.products_enable` List of products to enable for mirroring.
+- `app.scc.products_disable` list of products to exclude from mirroring.
+- `app.storage.class` Kubernetes storageclass.
+- `db.storage.class` Kubernetes storageclass.
+- `ingress.enabled` Enable or disable ingress.
+- `ingress.hosts[0]` DNS name at which the RMT service is be accessible from 
clients.
+- `ingress.tls[0].hosts[0]` DNS name at which the RMT service is be accessible 
from clients.
+- `ingress.tls[0].secretName` TLS ingress certificate.
+
 ## Deploying
 
 `helm install rmt ./helm -f myvalues.yaml`
 
+## Further info
+
+For more information on using RMT, refer to the [RMT 
Guide](https://documentation.suse.com/sles/html/SLES-all/book-rmt.html).
+
 ## Licensing
 
 `SPDX-License-Identifier: MIT`

Reply via email to