topic Re: SAS Viya 4 Install on Disconnected Enviroment in Administration and Deployment

SAS Viya 4 Install on Disconnected Enviroment

Phuchoang — Mon, 11 Aug 2025 09:02:30 GMT

My client requires to install SAS Viya on Disconnected Environment,

I prepare everything including mirrors registry, image mirrors. Deployment Operator.

But when I deploy software, Operator return Reconcile Failed with message can't Get https://ses.sas.download/ses/entitlements.json....

Can anyone suggest me any solution?

Re: SAS Viya 4 Install on Disconnected Enviroment

Jovian — Thu, 06 Nov 2025 07:59:26 GMT

Hi Phuchoang,

Have you checked if the mirror registry has been added to you local DNS.

Could you confirm if you have used this link to create your mirror registry in the darksite -Create a Mirror Registry at a Dark Site .

During deployment have you created the mirror.yaml as mentioned in the Optional Customization Add a Mirror Registry to Your SAS Viya Platform Deployment with the required changes being made.

I have attached below a sample of the required changes

#Sample mirror.yaml located at sas-bases/examples/mirror/mirror.yaml apiVersion: builtin kind: ImageTagTransformer metadata: name: image-transformer-sas-admin-content-loader-mirror imageTag: name: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-admin-content-loader newName: {{ MIRROR-HOST }}/viya-4-x64_oci_linux_2-docker/sas-admin-content-loader ---

You have to edit the {{ MIRROR-HOST }} with the fqdn/registry_name of you mirror registry.

#Edited mirror.yaml in site-config/ apiVersion: builtin kind: ImageTagTransformer metadata: name: image-transformer-sas-admin-content-loader-mirror imageTag: name: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-admin-content-loader newName: registry.darksite.com/lts2025.03/viya-4-x64_oci_linux_2-docker/sas-admin-content-loader ---

Here, registry.darksite.com is my mirror registry fqdn, and lts2025.03 is the name of the registry containing all the images.

Re: SAS Viya 4 Install on Disconnected Enviroment

gwootton — Thu, 06 Nov 2025 20:40:06 GMT

To use the SAS Deployment Operator in a air-gapped environment requires you set up an accessible HTTP server to serve up your repository warehouse.

You specify the URL to that server when creating the sasdeployment custom resource using the "--repository-warehouse" option.

[repository-warehouse-location] (optional)
The URL for the warehouse describing what should be deployed. This flag is needed if you are managing a dark environment.

Source: Create the SASDeployment Custom Resource:
https://go.documentation.sas.com/doc/en/sasadmincdc/v_069/dplyml0phy0dkr/p0nid9gu3x2cvln1pzpcxa68tpom.htm

The files that need to be served by that HTTP server are pulled into the --path location specified when you run mirrormgr (~/sas_repos by default). You'll see entitlements.json in there but I think it also makes use of the other paths there (except sas_repos/docker where the actual images were pulled).

Create a Mirror Registry at an Air Gapped Site:
https://go.documentation.sas.com/doc/en/sasadmincdc/v_069/dplyml0phy0dkr/n1f39x15xt82m4n13f7bu37l9qum.htm