search

sassoftware / viya4-deployment

This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71 stars 64 forks source link

2 default storage class prevent sas-catalog-services to start #88

Closed raphaelpoumarede closed 3 years ago

raphaelpoumarede commented 3 years ago

Hi there I was testing a fully automated deployment of stable 2020.1.5 in GKE this morning and everything worked well, except the sas-catalog pod. It turned out that sas-opendistro-default had an issue because 2 storage classes are defined image When checking the storage class I see that, indeed both "sas" and "standard" SC have the "default" flag. image

I modified the "sas" SC definition with storageclass.kubernetes.io/is-default-class: 'false', restarted the sas-opendistro-default statefulset, then the sas-catalog pod and the issue was solved. Is it expected ? should we prevent the "sas" SC to become the default one, if there is already a default ? Thanks

thpang commented 3 years ago

I know Norm worked on fixing this so the 'sas' storage class was not the default. Not sure if that codes been checked in. I'll touch base with @NormJohnIV on Monday.

thpang commented 3 years ago

This has been fixed. Pull the latest code and/or look at release 3.2.2.