GeezerVison

@tchughesiv @lokeshrangineni can use same directory operator-quickstart and can add new notebook example with Postgres in TLS mode with that all example related with operator will be same place. WDYT ?

@tchughesiv @lokeshrangineni can use same directory operator-quickstart and can add new notebook example with Postgres in TLS mode with that all example related with operator will be same place. WDYT ?

This example is having multiple notebooks isolates the group of steps. It appears to be the same notebooks as operator-quickstart based on the names but the content is different. It is going to be a further different after I add more description about volumeMounts and FEAST_CA_CERT_FILE_PATH. The abstraction i can do more with the demo notebook which is pretty close in both examples. The options i see are 1) combining them into one makes a big notebook with sub sections. 2) may be is it ok to add sub folders under operator-quickstart one with existing and another with postgres with tls.

any further preferences?

@tchughesiv @lokeshrangineni can use same directory operator-quickstart and can add new notebook example with Postgres in TLS mode with that all example related with operator will be same place. WDYT ?

This example is having multiple notebooks isolates the group of steps. It appears to be the same notebooks as operator-quickstart based on the names but the content is different. It is going to be a further different after I add more description about volumeMounts and FEAST_CA_CERT_FILE_PATH. The abstraction i can do more with the demo notebook which is pretty close in both examples. The options i see are 1) combining them into one makes a big notebook with sub sections. 2) may be is it ok to add sub folders under operator-quickstart one with existing and another with postgres with tls.

any further preferences?

if it's not fitting with existing example, then sure you can go with existing approach.

The idea is to create a note for an example like 03-TLS, then patch the CR to update the TLS configuration, and proceed further to verify that TLS is set up correctly and proceed with existing example accordingly. You will definitely need to configure PostgreSQL with TLS installation for that just delete the existing installation and setup it with TLS.

imo, the cleanest way would be to piggy-back off of the existing quickstart. Just add another .ipynb file, make it #3. And then continue what's already been done with the demo from #2. You could certainly create a subdir for the ssl bits.
https://github.com/feast-dev/feast/tree/master/examples/operator-quickstart

@lokeshrangineni that said, if its a huge ordeal to combine them... i'm completely fine keeping them separate as well

After removing the demo notebook there is not lot of synergy between operator-quickstart. installing postgres and uninstall jupyter notebook are totally different. Installing feast notebook is emphasizing more on the volume support and mounting secrets with different choices. so prefer to keep them separate as we discussed.

@lokeshrangineni to ensure this demo continues to work, you may want to specify a version of the bitnami/postgresql helm chart during install. future changes/release could derail this example.

I have incorporated in the commit

@lokeshrangineni WDYT Squashing commits to single ?

@redhatHameed @lokeshrangineni no need to squash them... the merge will