text stringlengths 2 1.5k |
|---|
SAS® Viya® Platform:
Deployment Guide
2023.08**This document might apply to additional versions of the software. Open this document in SAS Help Center and click
on the version in the banner to see all available versions.
SAS® Documentation
September 5, 2023 |
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2023. SAS® Viya® Platform: Deployment Guide . Cary, NC:
SAS Institute Inc.
SAS® Viya® Platform: Deployment Guide
Copyright © 2023, SAS Institute Inc., Cary, NC, USA
All Rights Reserved. Produced in the United States of America.
For a ... |
by the United States Government is subject to the license terms of this Agreement pursuant to, as applicable, FAR 12.212, DFAR
227.7202-1(a), DFAR 227.7202-3(a), and DFAR 227.7202-4, and, to the extent required under U.S. federal law, the minimum restricted rights
as set out in FAR 52.227-19 (DEC 2007). If FAR 52.227... |
Contents
Chapter 1 /Pre-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
ingress-nginx Vulnerability Mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Confidential Computing . . . . . . . .... |
Common Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Install the Orchestration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Create the SASDeployment Custom Resource . . . . . . . . . . . . . .... |
Configure the Connection to the Mail Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Configure Files Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configure Monitoring and Logging . . . . . . . . . . . . . . . . . . . . . . .... |
Configure SAS Data Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Configure SAS Dynamic Actuarial Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Deploy SAS Enterprise Session Monitor . . . . . . . . . . . . . . . . . . . . . . . .... |
Configure SAS Stress Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Configure SAS Visual Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configure SAS Visual Statistics . . . . . . . . . . . . . . . . . . . . . .... |
Configure SAS Viya Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configure SAS Viya Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Configure SAS Viya Programming . . . . . . . . . . . . . . . . . . . . . . . . ... |
Uninstall with the SAS Viya Platform Deployment Operator . . . . . . . . . . . . . . . . . . 127
Remove the SAS Viya Platform Deployment Operator Only . . . . . . . . . . . . . . . . . . 133
Uninstall Deployments That Do Not Use the Deployment Operator . . . . . . . . . . . . 133
Appendix 1 /(Optional) Using a Mirro... |
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Fields in the SASDeployment Custom Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Manage Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... |
Certframe Container Fails at init Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Issues with External PostgreSQL Server Size and Connections . . . . . . . . . . . . . . . 173
SAS Viya Platform Deployment Operator Reconcile Failures . . . . . . . . . . . . . . . . . 174
Performing U... |
1
Pre-installation Tasks
ingress-nginx Vulnerability Mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Confidential Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Plan the Workload Placement... |
Edit the kustomization.yaml for seccomp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configure the Mirror Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Add an imagePullSecret . . . . . . . . . . . . . . . . . . . . ... |
Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Additional Security ... |
ingress-nginx Vulnerability Mitigation
The SAS Viya platform requires configuration of the ingress-nginx controller. By
default, ingress-nginx supports custom snippets, which the SAS Viya platform
requires. ingress-nginx has discovered that the default setting of "allow-snippets=true
" exposes the deployment to known... |
Viya platform that lack the mitigation and that are sharing the ingress-nginx
controller.
nThe ingress-nginx controller is a supported version.
nThe Kubernetes cluster does not have any additional applications using the
ingress-nginx controller that do not support using the "annotation-value-word-
blocklist" annotat... |
The suggested values for the blocklist are supported by the SAS Viya platform: "load_module,lua_package,_by_lua,location,root,proxy_pass,serviceaccount,{,},\"
Confidential Computing
Note: Confidential computing is only supported on Microsoft Azure at this time. If
you are not deploying on Microsoft Azure, skip this se... |
aUpdate the Default Node pool VM type to one of the AMD SEV confidential
VMs. Here is an example:default_nodepool_vm_type = "Standard_DC8as_v5"
bUpdate the node pool availability zone and location. Here is an example:default_nodepool_availability_zones = ["1", "2", "3"] location = "East US"
If you are unsure of the a... |
monitoring servers. These issues can result in a non-functional
deployment.
Plan the Workload Placement
Note: If you have used a GitHub project, SAS Viya Infrastructure as Code (IaC), for
one of the cloud providers to provision your infrastructure components, the
procedures described in this section have already bee... |
deployment. When planning the placement of the workload, it is helpful to think
beyond the initial deployment and to also consider the Kubernetes maintenance life
cycle.
IMPORTANT SAS strongly recommends labeling and tainting all your
nodes, especially the CAS nodes. Note, however, that the connect workload
class i... |
more information about dynamically launched pods, see “connect” on page
6.
Workload Classes
Properties associated with the pods in your deployment describe the type of work
that they perform. By using the commands described in “Place the Workload on
Nodes” on page 9, you can configure where you want each class of po... |
time. Therefore, CAS can quickly drive every available CPU core to 100%
utilization. CAS also aggressively consumes RAM to process large volumes of
data as quickly as possible.
Because CAS was designed with performance as a primary objective, it must be
hosted on dedicated resources. Therefore, each CAS pod must be ... |
Studio sessions, and parallel compute processes that are executed as part of a
SAS Model Studio workflow.
connect
SAS/CONNECT provides the ability for clients to launch SAS compute
processes, the same processes described in “compute” on page 5, within a local
or remote SAS environment. The SAS/CONNECT Spawner is a... |
configured with Kubernetes guaranteed QoS.
If you do use the connect workload class, you must add a transformer to the
base kustomization.yam file. For more details, see the README file at $deploy/sas-bases/examples/sas-connect-spawner/README.md
(for Markdown format)
or at $deploy/sas-bases/docs/configure_sasconnect... |
names separated by a space. The term azure
is applied to all of the supported
cloud platforms because it represents a default SAS Viya platform deployment
setting that is not vendor-specific.6Chapter 1 / Pre-installation Tasks |
Considerations and Default Settings for
Workload Placement
The Kubernetes cluster administrator will recognize that each of the SAS Viya
platform workload classes should be managed differently. In situations where the
deployment has rigorous availability requirements and the Kubernetes cluster
software is being upg... |
class.
nNodes that host workloads for the cas and connect classes must be terminated
and started on different nodes before the underlying nodes can be maintained as
required.
Some aspects of workload placement are set by default during the SAS Viya
platform deployment, including both nodeAffinity and tolerations. I... |
Workload ClassDefault SettingsTolerate the following taints:
nworkload.sas.com/class=stateful:NoSchedule
nworkload.sas.com/class=stateless:NoSchedule
Compute workloadsPrefer to schedule on nodes that are labeled workload.sas.com/class=compute
Tolerate the taint workload.sas.com/class=compute:NoSchedule
CAS workloadsPre... |
nworkload.sas.com/class=casworker:NoSchedule
By default, the CAS operator uses auto-resourcing to utilize the full resources of a
node. When a CAS workload is scheduled to run on a specific node, no other
application pods can be scheduled to run on that node. If you want to disable auto-
resourcing and modify resourc... |
or $deploy/sas-bases/docs/auto_resources_for_cas_server_for_the_sas_viya_platform.htm
(for HTML
format).
If you deploy the SAS Viya platform into a cluster with untainted nodes, the
Kubernetes scheduler may attempt to schedule CAS onto those untainted nodes
instead of the nodes that have been labeled with workload.... |
nodes in your deployment:
To list the names of the nodes:kubectl get nodes
To assign a class of pods to a specific node:kubectl taint nodes node-name workload.sas.com/class=class-name:NoSchedule --overwritekubectl label nodes node-name workload.sas.com/class=class-name --overwrite
Note: The node-name can be the name o... |
kubectl get nodes -o=custom-columns=NAME:.metadata.name,LABELS:.metadata.labels,TAINTS:.spec.taints
After you have assigned the pods to nodes, to check the assignments:
Note: Because of the length of the command and the margin of the page, this
command appears as more than one line. The command should be entered as a ... |
described in the CR. The operator determines the release of the SAS Viya platform
that it is working with. It also uses the appropriately versioned tools for that release
while deploying and updating the SAS Viya platform software. Thus, a single
instance of the operator can manage all SAS Viya platform deployments ... |
Retrieve the Files Required by the SAS Viya
Platform Deployment Operator
Note: If you plan to use a mirror registry for the deployment of your SAS Viya
platform software, you should download and install SAS Mirror Manager before you
begin your deployment. For more information, see “Create a Mirror Registry” on
page... |
prefer.
3Click the Get Started link that is provided in your Software Order Email (SOE).
The my.sas.com page opens.
4Examine the order information. Ensure that you are working with the order you
expect.
5Select the Downloads tab. The line above the Asset Type table indicates the
release cadence and the version of ... |
assets for the version you intend to update to. The target version should be used
for deploying the deployment operator.
6Select Deployment Assets from the Asset Type list, then click Download to
download the files that are required to deploy your software.
7Save the TGZ file from the my.sas.com page to the direc... |
The kustomization.yaml file in the $operator-deploy directory is referred to as the
operator kustomization.yaml file throughout the documentation.
Note: Verify that you are using the correct directory for your changes: $operator-deploy/site-config
or $deploy/site-config
.12 Chapter 1 / Pre-installation Tasks |
Edit the transformer.yaml File
Replace the variables in the $operator-deploy/site-config/transformer.yaml
file as indicated in that file. Two patches must be updated.
nThe first patch sets the name of the ClusterRoleBinding resource that is needed
by the operator. The SAS Viya Platform Deployment Operator requires cl... |
is also used in the base kustomization.yaml file since you are also deploying the
SAS Viya platform into it.---apiVersion: builtinkind: PatchTransformermetadata: name: patch-transformer-sas-deployment-operatorpatch: |- # name: MUST BE PROVIDED BY USER AND UNIQUE IN CLUSTER. - op: replace path: /metadata/name ... |
Edit the kustomization.yaml for Cluster-Wide Mode
If the operator is being deployed in namespace mode, skip this section. However, if
the operator is being deployed in cluster-wide mode, edit the operator
kustomization.yaml to uncomment the reference to site-config/cluster-wide-transformer.yaml
. Here is an example o... |
you are using Red Hat OpenShift, copy the mirror-flattened.yaml file.
2Revise the mirror configuration file based on the infrastructure you are using for
your deployment.
nIf you are deploying on any cloud provider other than Red Hat OpenShift,
open the mirror.yaml file and replace each instance of {{ MIRROR-HOST }} ... |
FQDN/registry-namespace/sasdeployment
Here is an example:example.company.com/registry-namespace/sasdeployment
After replacing all instances of {{ MIRROR-HOST }}
, save and close the file.
nIf you are deploying on Red Hat OpenShift, modify the mirror-flattened.yaml
file.
1Find the image registry name and port:oc get s... |
file as the last entry in the transformers section. For example, if you are
deploying on any cloud provider except Red Hat OpenShift and you copied the
mirror.yaml file to the top level of the $operator-deploy/site-config
directory,
the entry would look like this:transformers:- site-config/transformer.yaml- site-co... |
Add an imagePullSecret
Note: If you are not using a mirror registry or if you are using a mirror registry but
authentication is not required, skip this section.
If SAS content has been mirrored, and that mirror requires authentication, you must
configure an imagePullSecret and patch that secret into the SAS Viya Plat... |
OpenShift includes instead of creating a new one.
1Find the name of the secret:kubectl -n name-of-namespace get secret | grep default-dockercfg
16 Chapter 1 / Pre-installation Tasks |
The output looks like this:default-dockercfg-#####
2Edit the operator kustomization.yaml file by adding a patch that contains a
reference to the secret:patches:- patch: |- - op: add path: /spec/template/spec/imagePullSecrets value: - name: output-of-step-1 target: kind: Deployment name: sas-de... |
The do-not-proxy-list is a comma-separated list of host names, fully qualified host
names, and IP addresses that the proxy should ignore.
Here is an example of the deployment.yaml file with values:Deploy the SAS Viya Platform Deployment Operator 17 |
containers: - args: - reconcile command: [] env: - name: HTTP_PROXY value: "http://webproxy.example.com:5000" - name: HTTPS_PROXY value: "http://webproxy.example.com:5000" - name: NO_PROXY value: "localhost,nopr... |
Operator in namespace mode, the SAS Viya platform deployment must be
performed in the same namespace that was used for the operator.
If you have not already done so, create a namespace for your SAS Viya platform
deployment.
2Create the directory for your deployment assets.18 Chapter 1 / Pre-installation Tasks |
nIf you have created a mirror registry, you have already created the $deploy
directory and should skip to step 3.
nCreate a directory on the kubectl machine or on a machine that can be
reached by your kubectl machine:mkdir directory-name
Note: If you have deployed the SAS Viya Platform Deployment Operator, the
new d... |
release cadence and the version of SAS Viya platform software that you will
deploy. If you want to deploy a different version, find the listing for that version on
the page.
6Select Deployment Assets from the Asset Type list, then click Download to
download the files that are required to deploy your software.
Sa... |
aCreate a new directory parallel to the $deploy directory in which to store your
license and *-certs.zip files.mkdir directory-name
You should use a name that is meaningful to you. The directory is referred to
as $license in this guide. Replace $license with the directory name that you
prefer.
bCopy the *-certs.zip ... |
Security Context Constraints and Service Accounts
Overview
A deployment in OpenShift requires multiple custom security context constraints
(SCCs) to provide permissions to SAS Viya platform services. SCCs are required in
order to enable the Pods to run. (Pods provide essential SAS Viya platform
components.) In addit... |
sas-cas-server
Every deployment on OpenShift must apply one of the following SCCs for the CAS
server.
Why the SCC is needed: CAS relies on SETUID, SETGID, and CHOWN
capabilities. CAS is launched by a SETUID root executable called caslaunch. By
default, caslaunch starts the CAS controller running under the runAsUser/... |
Therefore, at a minimum, the cas-server-scc SCC must be applied. If the custom
group "CAS Host Account Required" is used, apply the cas-server-scc-host-launch
SCC. If the CAS server is configured to use a custom SSSD, apply the cas-server-
scc-sssd SSC. For more information on enabling SSSD, see “Use Kerberos
Connec... |
(for HTML format).
Why the SCC is needed: The SAS/CONNECT Launcher must be able to launch the
SAS/CONNECT Server under end user identity.
1Apply the SCC with the following command:kubectl apply -f sas-bases/examples/sas-connect-spawner/openshift/sas-connect-spawner-scc.yaml
2Bind the SCC to the service account with ... |
1There is no SCC to apply.
2Bind the SCC to the service account with the following command:oc -n name-of-namespace adm policy add-scc-to-user nonroot -z sas-esp-project
sas-microanalytic-score
To determine if the sas-microanalytic-score SCC is needed for your deployment,
check for a README file in your deployment asse... |
sas-model-publish-kaniko
To determine if the sas-model-publish-kaniko service account exists in your
deployment, check for a README file in your deployment assets at $deploy/sas-bases/examples/sas-model-publish/kaniko/README.md
. If the README file is
present and you plan to publish models with SAS Model Manager or S... |
Why the SCC is needed: The sas-model-repository pod requires a service account
with privileges if the Python environment is made available through an NFS mount.
NFS volumes are not permitted in the restricted SCC, so an SCC that has NFS in
the allowed volumes section is required.
For more information, see the README... |
option
enabled, and runAsUser
set to RunAsAny
.
Therefore, before you apply the sas-opendistro-scc.yaml file, you must modify it to
enable these privileges. For the instructions to modify them, see the “Modify sas-
opendistro-scc.yaml for sysctl-transformer.yaml” section of the README file at $deploy/sas-bases/examp... |
sets the kernel parameter, it terminates, and the OpenSearch software will then
proceed to start as a non-privileged container.
1Apply the SCC with the following command:kubectl apply -f sas-bases/examples/configure-elasticsearch/internal/openshift/sas-opendistro-scc.yaml
2Bind the SCC to the service account with the ... |
SAS Watchdog
SAS Watchdog is included in every SAS Viya platform deployment. If you choose to
deploy SAS Watchdog, the SCC is required. For more information, see the
README file at $deploy/sas-bases/overlays/sas-programming-environment/watchdog/README.md
(for Markdown format) or at $deploy/sas-bases/docs/configuring... |
step.
1If your deployment does not require hostPath volume mounts, bind the nonroot
SCC to the sas-programming-environment service account using this command:oc -n name-of-namespace adm policy add-scc-to-user nonroot -z sas-programming-environment
2If your deployment requires hostPath volume mounts, bind the hostmount... |
1Modify the CAS SCC you chose to use at “Security Context Constraints and
Service Accounts” on page 21.
aSet allowHostDirVolumePlugin
to true.
bAdd hostPath
to the list of volume types. Here is an example:volumes:- configMap- downwardAPI- emptyDir- persistentVolumeClaim- projected- secret- nfs- hostPath
2Run the fol... |
TLS
Because OpenShift uses routes instead of Ingress, the security component listed in
the initial kustomization.yaml file must be revised. Here is the original
kustomization.yaml content:components:- sas-bases/components/security/core/base/full-stack-tls- sas-bases/components/security/network/networking.k8s.io/ingre... |
├── docs/├── examples/├── extras/└── overlays/
The examples subdirectory contains files that are organized by categories, such as
CAS and security, that control the configuration of your deployment. README.md
files describe specific configuration settings and the files and modifications that are
required to enable t... |
contains configuration files for special deployment options. It is also subdivided into
examples and overlays subdirectories that act in the same way as the higher level
examples and overlays directories.
The base and components subdirectories do not contain any files that you should
revise.
$deploy/site-config Dire... |
Organization
Because the $deploy/site-config
directory contains files that you modify, you
should organize the directory according to your needs. However, it is important that
you plan the organization before you continue the deployment process. You should
organize your files in the site-config directory so that yo... |
kustomization.yaml file. Therefore, you can consider organizing the site-config
directory according to the blocks in kustomization.yaml. Here is an example:$deploy/├── sas-bases/└── site-config/ ├── configMapGenerator/ ├── patches/ ├── resources/ ├── secretGenerator/ └── transformers/
Directory Structur... |
Directories for the SAS Viya Platform Deployment
Operator
Note: If you are deploying your SAS Viya platform using Kubernetes commands or
the sas-orchestration command, skip this section.
Deploying with the SAS Viya Platform Deployment Operator requires a more
extensive directory structure that is based on the struct... |
and $deploy/site-config
subdirectories. You should
have a uniquely named $deploy directory for each SAS Viya platform deployment.
Note: Do not put additional files in the $deploy directory unless directed to do so by
SAS documentation or SAS Technical Support. 30 Chapter 1 / Pre-installation Tasks |
2
Installation
Initial kustomization.yaml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Create the File . .... |
Add Forward Proxy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configure Container Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Enable Multi-tenancy . . . . . . . . . . . . . . . . . . . . . .... |
Configure OpenSearch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configure SAS/CONNECT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configure SAS Programming Run-Time Environment . . . . . . . . ... |
Install the Orchestration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Create the SASDeployment Custom Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Add an imagePullSecret for the SAS Viya Platform Namespace . . . . . ... |
Deploy the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Deployment Using the SAS Viya Platform Deployment Operator . . . . . . . . . . . . . . . . . 85
Deployment Using the sas-orchestration Command . . . . . . . . . . . . . . . .... |
Sign In as the sasboot User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Promotion and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Initial kustomization.yaml File
Overview
The b... |
configurations for deployments. The full list of configurations that are available for
your order can be accessed in either Markdown or HTML. To see the index of
READMES available for your order in Markdown, go to /$deploy/sas-bases/README.md
. To see the index of READMEs available for your order in HTML, go to $depl... |
file for the current version of the software. Although the deployment notes
focus on updates, the same issues apply to a base kustomization.yaml file
(and other .yaml files) that was created for the previous version of the
software but is being used for the current version of the software.
Note: The README files th... |
should be replaced with a namespace name, such as deploy
.namespace: {{ NAME-OF-NAMESPACE }} 1resources:- sas-bases/base- sas-bases/overlays/network/networking.k8s.io 2- site-config/security/openssl-generated-ingress-certificate.yaml 3- sas-bases/overlays/cas-server- sas-bases/overlays/crunchydata/postgres-operator- sa... |
patches:- path: site-config/storageclass.yaml 7 target: kind: PersistentVolumeClaim annotationSelector: sas.com/component-name in (sas-backup-job,sas-data-quality-services,sas-commonfiles,sas-cas-operator,sas-pyconfig)# License information# secretGenerator:# - name: sas-license# type: sas.com/license# behavi... |
from scheduling non-CAS workloads on them. If you enable the CAS auto-
resources option, your designated CAS nodes must already be labeled. For
more information, see “Plan the Workload Placement” on page 4. If the nodes
are not labeled, you must disable auto-resources and use hardcoded default
resource settings. To ... |
7
For information about the storageclass.yaml file, see “Specify
PersistentVolumeClaims to Use ReadWriteMany StorageClass” on page 76.8
The SAS_SERVICES_URL
variable is used to provide the value for the
SERVICESBASEURL option in compute server sessions. It should point to
the host name and port of the cluster's Ing... |
modify the appropriate .yaml file.
5If you want to make changes to your configuration, see “Common
Customizations” on page 36, which is a description of the most frequently used
configuration options. To see a list of all the configuration options for your
software, go to/$deploy/sas-bases/README.md
for Markdown ve... |
Common Customizations
Overview
Configuring your SAS Viya platform deployment, including setting environment
variables, is performed by modifying example and overlay files in your deployment
assets and then adding references to those files to the base kustomization.yaml file.
This section describes the most common de... |
requires conversation between the Kubernetes administrator and the SAS
administrator. The Kubernetes administrator for your site should inform the
SAS administrator of the options available for the deployment based on the
README files in the deployment assets, perhaps even sharing the README
files and their descrip... |
Add a Mirror Registry to Your SAS Viya
Platform Deployment
Note: Complete this task only if you are deploying your SAS Viya platform with
Kubernetes commands or the sas-orchestration command. If you are deploying with
the SAS Viya Platform Deployment Operator, you have already completed this task
while deploying th... |
In the value for IMAGE_REGISTRY
:
nregistry-host is required.
nregistry-port is optional. If registry-port is omitted, the colon (:) that precedes
it should be omitted also.
nregistry-namespace is optional. registry-namespace is not the same as the
Kubernetes namespace. If registry-namespace is omitted, the sla... |
Using Kubernetes Commands on Red Hat
OpenShift
1Copy the mirror-flattened.yaml file from sas-bases/examples/mirror/
to the
site-config directory.
2Modify the mirror-flattened.yaml file.
aFind the image registry name and port:oc get svc -n name-of-registry-namespace
The output looks like this:Name Type ... |
to the transformers block, immediately after the entry for sas-bases/overlays/required/transformers.yaml
. Here is an example:transformers:...- sas-bases/overlays/required/transformers.yaml- site-config/mirror-flattened.yaml
4Add the following content to the configMapGenerator block in the base
kustomization.yaml file... |
Using the sas-orchestration Tool on Red Hat
OpenShift
Add content to the configMapGenerator block in the base kustomization.yaml file.
1Find the image registry name and port:oc get svc -n name-of-registry-namespace
The output looks like this:Name Type Cluster-IP External-IP Ports Ageimage-r... |
2Here is the command to obtain the unencoded value of the .dockerconfigjson
field of imagePullSecret required for {{ MY-IMAGEPULLSECRET }}
. The
credentials used in these examples vary by cloud provider and by local cloud
provider conventions adopted by your organization.kubectl create secret docker-registry --dry-r... |
should be replaced with the output of the command
in step 2.
You can also optionally save .dockerconfigjson to a local file and reference it in
your secretGenerator with the “files” keyword instead of “literals”.
Red Hat OpenShift Alternative
If you are deploying on Red Hat OpenShift, you can use the contents of an e... |
kubectl -n name-of-namespace get secret output-from-step-1 --output="jsonpath={.data.\.dockercfg}" | base64 --decode > name-of-namespace.default.dockercfg.json
3Edit the secretGenerator block of the base kustomization.yaml file:secretGenerator:- name: sas-image-pull-secrets behavior: replace type: kubernetes.io/docke... |
platform deployment, these environment variables must be defined on the Update
Checker cron job:
nHTTP_PROXY
nHTTPS_PROXY
nNO_PROXY
1Copy $deploy/sas-bases/examples/update-checker/proxy_transformer.yaml
file to $deploy/site-config/update-checker/proxy_transformer.yaml
.Common Customizations 41 |
2In the copied file, replace the value for HTTP_PROXY
with the host name, the fully
qualified host name, or the IP address of the HTTP proxy. Replace the value for HTTPS_PROXY
with the host name, the fully qualified host name, or the IP address
of the HTTPS proxy. Replace the value for NO_PROXY
with a comma-separa... |
can be used only to set new property values that have not already been set.
Therefore, SAS recommends that you do not use the sitedefault.yaml file for the
initial deployment of your SAS Viya platform, except where specifically described in
this guide. You can, however, use a sitedefault file from a previous SAS Viya... |
Configure TLS
Follow these steps to deploy using openssl as the certificate generator.
Note: The example kustomization.yaml file, located at “Create the File” on page 33,
represents a deployment with NGINX TLS for full-stack TLS mode using openssl to
generate the ingress certificate.
1Copy the $deploy/sas-bases/examp... |
Replace ingress-technology with the technology that handles traffic entering
your cluster:
nnetworking.k8s.io/ingress/nginx.ingress.kubernetes.io
nroute.openshift.io/route
Replace TLS-mode with one of the following based on the TLS mode you are
deploying:Common Customizations 43 |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 10