Skip to content

Commit 027614a

Browse files
authored
Merge pull request #653 from sassoftware/pr-pscloud-1
docs: replace Updating SAS Viya Manually section (PSCLOUD-1)
2 parents 384abd1 + 331bbd1 commit 027614a

File tree

2 files changed

+5
-13
lines changed

2 files changed

+5
-13
lines changed

.github/workflows/linter-analysis.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,6 @@ jobs:
5959
run: ansible-galaxy install -r ./requirements.yaml
6060

6161
- name: Run ansible-lint Action
62-
uses: ansible/ansible-lint-action@v6.17.0
62+
uses: ansible/ansible-lint@main
6363
env:
6464
ANSIBLE_ROLES_PATH: "./roles"

README.md

Lines changed: 4 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@
2525
- [Creating and Managing Deployments](#creating-and-managing-deployments)
2626
- [DNS](#dns)
2727
- [SAS/CONNECT](#sasconnect)
28-
- [Updating SAS Viya Manually](#updating-sas-viya-manually)
2928
- [Troubleshooting](#troubleshooting)
3029
- [Contributing](#contributing)
3130
- [License](#license)
@@ -34,6 +33,10 @@
3433

3534
## Overview
3635

36+
- This project can only be used for patch updates that use the exact same manifest as the existing deployment.
37+
- Updating to a new SAS Viya platform version, cadence, or a new software offering is not supported using this project.
38+
- For more information about updating your software, see [The SAS Viya Deployment as a Code project does not perform updates](https://sas.service-now.com/csm?id=kb_article_view&sysparm_article=KB0041450).
39+
3740
This project contains Ansible code that creates a baseline cluster in an existing Kubernetes environment for use with the SAS Viya platform, generates the manifest for a SAS Viya platform software order, and then deploys that order into the specified Kubernetes environment. Here is a list of tasks that this tool can perform (also see [playbook overview](./playbooks/README.md) for info on the default tasks):
3841

3942
- Prepare Kubernetes cluster
@@ -340,21 +343,10 @@ In the above example, the ingress controller's LoadBalancer endpoint is 52.52.52
340343
- An A record (such as `example.com`) that points to the 52.52.52.52 address
341344
- A wildcard CNAME (`*.example.com`) that points to example.com
342345

343-
344346
#### SAS/CONNECT
345347

346348
When running the `viya` action with `V4_CFG_CONNECT_ENABLE_LOADBALANCER=true`, a separate loadbalancer service is created to allow external SAS/CONNECT clients to connect to the SAS Viya platform. You will need to register this LoadBalancer endpoint with your DNS provider such that the desired host name (for example, connect.example.com) points to the LoadBalancer endpoint.
347349

348-
349-
### Updating SAS Viya Manually
350-
351-
Manual steps are required by the SAS software to update a SAS deployment in an existing cluster. As a result, viya4-deployment does not perform updates. The viya4-deployment tools can perform subsequent `viya,install` tasks if you are simply reapplying the same software order into the cluster.
352-
353-
If you have an existing deployment that you performed with the viya4-deployment project, take the following steps in order to update the SAS Viya platform:
354-
355-
- Follow the instructions in [Updating Software](https://documentation.sas.com/?cdcId=sasadmincdc&cdcVersion=default&docsetId=k8sag&docsetTarget=titlepage.htm) in the SAS Viya Platform Operations Guide.
356-
- You are expected to modify the steps that are described in the SAS Viya Platform Operations Guide to accommodate the slightly different directory structure
357-
358350
### Troubleshooting
359351

360352
See the [Troubleshooting](./docs/Troubleshooting.md) page.

0 commit comments

Comments
 (0)