Hello I see a large number of jobs for example sas-update-checker, sas-deployment-operator-reconcile ,sas-backu-job etc listed when I check for completed jobs using kubectl. Can these completed jobs be deleted? I always delete any adhoc start / stop jobs I create. ... View more

Hello Wondering if there are any downsides in moving from LTS to Stable Cadence (Other than support level)? Any thing to look out for? ... View more

Hello The community article Configure a Compute Context with Pre-started Compute Servers from the command-line    has demonstrated that we can have multiple pre-started compute -servers. Wondering if there is a way to load balance these compute servers. The idea is that when a job is started using rest-api  and using the new compute context, it should go to an idle compute server. ... View more

Hello We have SAS Viya4 running on AWS. The context "SAS Job Execution compute context"   was copied and a new context with the name "SAS Job Execution compute context_copy" was created. I added the attributes  reuseServerProcesses=true and runServerAs. The idea was to create a reusable compute server. When a job is executed using Rest API from postman, the following error occurs. The error disappears when the attributes are removed. Job Error Failed to create a SAS Workload Orchestrator job: status=403 FORBIDDEN traceId: 89ef1a68aee6ff6e path: /launcher/processes path: /compute/contexts/24d3c34b-d524-45c0-96fd-3c4634b65b8f/sessions correlator: 8037bd5c-a40f-4653-b219-875a6bcb4d08;f67e1474-6626-413c-80ee-16415aa5f17c The client is not authorized to submit jobs. Requesting the community for assistance/ideas on how to resolve this. ... View more