feat: Added feast Go operator db stores support

[tmihalac]

What this PR does / why we need it:

This PR adds db stores persistence configuration options to the FeatureStore CRD.
DB store para

• Support is provided to the Online service, Offline service and Registry service.
• Follows definitions in RFC #42
• Configuration examples are provided in config/samples

kind: FeatureStore
metadata:
  name: sample-s3-registry
spec:
  feastProject: my_project
  services:
    onlineStore:
      persistence:
        store:
          type: postgres
          secretRef: 
            name: _SECRET_NAME_ # Secret keys should be placed as-is under the `type` (e.g postgres) key or under the secretKeyName if specified
          secretKeyName: my-postgres # The secret key the db parameters are in (optional parameter)
    offlineStore:
      persistence:
        store:
          type: postgres
          secretRef: 
            name: _SECRET_NAME_ # Secret keys should be placed as-is under the `type` (e.g postgres) key or under the secretKeyName if specified
          secretKeyName: my-postgres # The secret key the db parameters are in (optional parameter)
    registry:
      local:
        persistence:
          store:
            type: sql
            secretRef: 
              name: _SECRET_NAME_ # Secret keys should be placed as-is under the `type` (e.g sql) key or under the secretKeyName if specified
            secretKeyName: my-postgres # The secret key the db parameters are in (optional parameter)

kind: Secret
apiVersion: v1
metadata:
  name: my-secret
  namespace: test
  uid: b410b5e5-857b-4611-acc3-1302b8c6c68c
  resourceVersion: '62030'
  creationTimestamp: '2024-11-19T20:25:15Z'
  managedFields:
    - manager: kubectl-create
      operation: Update
      apiVersion: v1
      time: '2024-11-19T20:25:15Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:data':
          .: {}
          'f:mykey': {}
        'f:type': {}
data:
  postgres: |
    host: DB_HOST
    port: DB_PORT
    database: DB_NAME
    db_schema: DB_SCHEMA
    user: DB_USERNAME
    password: DB_PASSWORD
    sslmode: verify-ca
    sslkey_path: /path/to/client-key.pem
    sslcert_path: /path/to/client-cert.pem
    sslrootcert_path: /path/to/server-ca.pem
  sql: |
    path: postgresql://postgres:mysecretpassword@127.0.0.1:55001/feast
    cache_ttl_seconds: 60
    sqlalchemy_config_kwargs:
        echo: false
        pool_pre_ping: true
type: Opaque

Which issue(s) this PR fixes:

Relates to #4783

[dmartinol]

@tmihalac the issue you are referring to is already closed. @tchughesiv should we create a new one or reopen it?

[dmartinol]

In the description, the postgres type is not supported by registry, pls change it to sql (and also add a sql key to the secret name)

    registry:
      local:
        persistence:
          store:
          type: postgres

[tchughesiv]

@tmihalac @dmartinol we should be opening new issues for operator PRs

[tchughesiv]

@tmihalac please rebase on master branch

[tchughesiv]

@tmihalac please open a new gh issue for this PR

[tchughesiv]

@tmihalac should your descrip example be fixed? i'd imagine it will look like this? with the secretKeyName pulled back to under store?

kind: FeatureStore
metadata:
  name: sample-s3-registry
spec:
  feastProject: my_project
  services:
    onlineStore:
      persistence:
        store:
          type: postgres
          secretRef: 
            name: _SECRET_NAME_ # Secret keys should be placed as-is under the `type` (e.g postgres) key or under the secretKeyName if specified
          secretKeyName: my-postgres # The secret key the db parameters are in (optional parameter)

[tmihalac]

@tmihalac should your descrip example be fixed? i'd imagine it will look like this? with the secretKeyName pulled back to under store?

kind: FeatureStore
metadata:
  name: sample-s3-registry
spec:
  feastProject: my_project
  services:
    onlineStore:
      persistence:
        store:
          type: postgres
          secretRef: 
            name: _SECRET_NAME_ # Secret keys should be placed as-is under the `type` (e.g postgres) key or under the secretKeyName if specified
          secretKeyName: my-postgres # The secret key the db parameters are in (optional parameter)

You are right fixing it now

[tmihalac]

Done

[shuchu]

Hi team, I see a lot of contributions here! but please beware that there is a PR which will have lots of Golang code change: #4665

[dmartinol]

Hi team, I see a lot of contributions here! but please beware that there is a PR which will have lots of Golang code change: #4665

@shuchu I hope the operator lives in a separate folder of the repo, so we're not expecting any "interference" from the other PR. These components seem to be independent of each other, but please advise if you think there is something we should look at instead. Thanks!

[dmartinol]

In the description, the postgres type is not supported by registry, pls change it to sql (and also add a sql key to the secret name)
@tmihalac be aware that the example in the description refers to a secretKeyName: my-postgres that does not exist in the given Secret. Also, for the registry you should use the default key name, e.g. sql instead of either postgres or my-postgres.

[dmartinol]

Leftovers are tracked in #4793

[shuchu]

Hi team, I see a lot of contributions here! but please beware that there is a PR which will have lots of Golang code change: #4665

@shuchu I hope the operator lives in a separate folder of the repo, so we're not expecting any "interference" from the other PR. These components seem to be independent of each other, but please advise if you think there is something we should look at instead. Thanks!

sorry, my bad. I didn't pay attention to the folder structure. No advisee from my side. Actually I'm learning form the code write by you all as I'm starting to write Golang codes.