Kubenetes Pod and Yellowfin

Deannah shared this question 23 days ago
Answered

We have our YellowFin deployed to a kubenetes Pod, and we are trying to come up with the best way to allow our team to customise and deploy the CSS/ Headers / footers etc to make the layout as we need it.Assuming we have a local filesystem containing the changes that we want to make to ROOT CSS and files, (Yellowfin\appserver\webapps\ROOT\*) and we can put that into a git repo…..Would it be preferable to restart a kubernetes pod to pull in a new version of a docker image every time the new html/css customisations need to be deployed (ie. restarting the whole of YF every time)

OR

dynamically linking html/css customisation files via NFS (AWS EFS) or some other means (background sync with s3 maybe?) without stopping/restarting the yellowfin instance?In your experience, which option is best, or is there a third option that we have not considered yet?

Comments (2)

photo
1

Hi Deannah,

Thanks for reaching out to support with your question.

I did a little testing, and I was able to add new files to the ROOT folder, as well as make changes to these files, and have them apply in the UI, all without having to restart Yellowfin. See video attached.


So It's looking like you can make these CSS changes without having to take anything down for maintenance. It would just be a matter of finding a deployment method that works for you. Hopefully this answers your question?

Thanks,

Eric

photo
1

HI Deannah,

I'm going to go ahead and mark this ticket as Answered at this time. feel welcome to reply here with any related inquiries.

Thanks,

Eric