I did search a bit more, and I understand now the situation:     pathType: Prefix is intended for paths that only need to match prefixes without regex, so it won't support complex patterns like (/|$)(.*) . pathType: ImplementationSpecific allows NGINX to handle the path matching as it sees fit, which includes the ability to use regex patterns.   To fix this, change the pathType for this Ingress path to ImplementationSpecific : Edit your Ingress resource configuration. Locate the pathType for /types(/|$)(.*) . E.g. Adapt it to ImplementationSpecific :   paths: - path: /types(/|$)(.*) pathType: ImplementationSpecific backend: service: name: your-service-name port: number: 80 This being said, this is not documented by SAS, it is Kubernetes specific. Therefore chances are that it might not be supported by SAS officially. What scripts are you using, the IaC/Deployment scripts? In that case you should reach out to the creators via the GitHub projects. Else, you probably should reach out to SAS Technical Support, to get a supported version of the fix.   ... View more

Hi, I agree, you might need SAS Technical Support for this. The only thing I can suggest for now: - Do have your admins to check if the requirements are properly configured: https://documentation.sas.com/doc/en/itopscdc/v_057/itopssr/p03lkog7sche30n16nz48rhqe2ka.htm - when they are 100% they are properly set, they can a) chech the driver connection without SAS and b) check the logs in the pods ... View more

Hi, I think you received good replies here. Indeed, your IT probably has a backup strategy that any part of your infrastructure will follow suit. However I am guessing you are part of IT and you would like to know the specifics for SAS when running on Kubernetes pods, since it’s probably different in your infrastructure. So, yes indeed, regarding incremental and full backups, it’s probably pre-defined at storage level. Let’s find it what you have in SAS: - VMs K8s cluster with nodes and Persistent Volumes (local or shared storage). - Stateful, Stateless, Compute, CAS and System nodes (at least) - A jump server where you operate SAS Viya from, with your kustomize playbooks and deployment assets. For the VMs and pods, normal backups, run only when a new version is deployed, is the bare minimum. Any more frequent is fine but won’t make a difference. Stateful nodes: One key aspect was mentioned by @gwootton, SAS offers an internal backup. This one is critical, as you can do a backup of all the storage, however you need to ensure the state of the system, which is in the Stateful nodes, and will not be in storage unless you run this internal backup, as these services run in memory. If you align to run the internal backup before your PVs backup with incremental backup you are good to go. - Stateless: nothing in particular, unless you want to keep your logs, which is a different discussion. - Compute: similar as above: the local PVs for SASWORK or UTILLOC won’t need any backup unless really needed by users and batch processes. Of course any data related PVs and datasources (git, databases, etc) will need daily incremental backups. - CAS: you probably want at least a daily backup of CAS_CACHE PVs. For the data backups, similar as Computer. - System and jump server: probably daily backups are a good idea too. 😉 ... View more