SUSE Multi-Linux Manager 5.1 Proxy Deployment on K3s

1. Installing K3s

SUSE Multi-Linux Manager Proxy is supported on K3s running on top of SL Micro in a single node cluster. If you need to deploy it in any other Kubernetes environment, contact support for evaluation.

On the container host machine, install K3s (replace <K3S_HOST_FQDN> with the FQDN of your K3s host):

curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--tls-san=<K3S_HOST_FQDN>" sh -

2. Installing Tools

The installation requires the mgrpxy and helm packages.

The mgrpxy and helm packages are available in the SUSE Multi-Linux Manager Proxy product repositories.

To install it, run:

transactional-update pkg install helm mgrpxy

Reboot

2.1. Generate the Proxy Configuration with Web UI

Procedure: Generating a Proxy Container Configuration Using Web UI

In the Web UI, navigate to Systems Proxy Configuration and fill the required data:
In the Proxy FQDN field type fully qualified domain name for the proxy.
In the Parent FQDN field type fully qualified domain name for the SUSE Multi-Linux Manager Server or another SUSE Multi-Linux Manager Proxy.
In the Proxy SSH port field type SSH port on which SSH service is listening on SUSE Multi-Linux Manager Proxy. Recommended is to keep default 8022.
In the Max Squid cache size [MB] field type maximal allowed size for Squid cache. Recommended is to use at most 80% of available storage for the containers.

2 GB represents the default proxy squid cache size. This will need to be adjusted for your environment.
In the SSL certificate selection list choose if new server certificate should be generated for SUSE Multi-Linux Manager Proxy or an existing one should be used. You can consider generated certificates as SUSE Multi-Linux Manager builtin (self signed) certificates.

Depending on the choice then provide either path to signing CA certificate to generate a new certificate or path to an existing certificate and its key to be used as proxy certificate.

The CA certificates generated by the server are stored in the /var/lib/containers/storage/volumes/root/_data/ssl-build directory.

For more information about existing or custom certificates and the concept of corporate and intermediate certificates, see Import SSL Certificates.
Click Generate to register a new proxy FQDN in the SUSE Multi-Linux Manager Server and generate a configuration archive (config.tar.gz) containing details for the container host.
After a few moments you are presented with file to download. Save this file locally.

2.2. Generate Proxy Configuration With `spacecmd` and Self-Signed Certificate

You can generate a Proxy configuration using spacecmd.

Procedure: Generating Proxy Configuration with spacecmd and Self-Signed Certificate

SSH into your container host.

Execute the following command replacing the Server and Proxy FQDN:

mgrctl exec -ti 'spacecmd proxy_container_config_generate_cert -- dev-pxy.example.com dev-srv.example.com 2048 email@example.com -o /tmp/config.tar.gz'

Copy the generated configuration from the server container:
```
mgrctl cp server:/tmp/config.tar.gz .
```

2.3. Generate Proxy Configuration With `spacecmd` and Custom Certificate

You can generate a Proxy configuration using spacecmd for a custom certificates rather than the default self-signed certificates.

Procedure: Generating Proxy Configuration with spacecmd and Custom Certificate

SSH into your Server container host.

Execute the following command replacing the Server and Proxy FQDN:

for f in ca.crt proxy.crt proxy.key; do
  mgrctl cp $f server:/tmp/$f
done
mgrctl exec -ti 'spacecmd proxy_container_config -- -p 8022 pxy.example.com srv.example.com 2048 email@example.com /tmp/ca.crt /tmp/proxy.crt /tmp/proxy.key -o /tmp/config.tar.gz'

Copy the generated configuration from the server container:
```
mgrctl cp server:/tmp/config.tar.gz .
```

3. Deploying the SUSE Multi-Linux Manager Proxy Helm Chart

To configure the storage of the volumes to be used by the SUSE Multi-Linux Manager Proxy pod, define persistent volumes for the following claims. If you do not customize the storage configuration, K3s will automatically create the storage volumes for you.

The persistent volume claims are named:

squid-cache-pv-claim
package-cache-pv-claim
tftp-boot-pv-claim

Create the configuration for the SUSE Multi-Linux Manager Proxy as documented in SUSE Multi-Linux Manager 5.1 Proxy Deployment. Copy the configuration tar.gz file and then install:

mgrpxy install kubernetes /path/to/config.tar.gz

For more information see https://kubernetes.io/docs/concepts/storage/persistent-volumes/ (kubernetes) or https://rancher.com/docs/k3s/latest/en/storage/ (K3s) documentation.