OLS-2378: Generic Provider Config for LCore supported providers.

[sriroopar]

Description

This PR introduces Generic Provider Configuration support for LCore (Llama Stack) backend, enabling flexible LLM provider configuration beyond the predefined types.

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up dependent library

Related Tickets & Documents

• Related Issue # OLS-2378
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.

  • Configured OLS to use LCore as backend, as changes will not work with appserver backend.
  • Applied a valid config using remote:: openai as provider type.
  • Verified llama stack configmap generation and validation rules manually.
  • Checked liveliness of endpoint with openai provider and passed a query and verified that the response is valid.
  • Also verified with an invalid provider type.

• How were the fix/results from this change verified? Please provide relevant screenshots or results.

[openshift-ci-robot]

@sriroopar: This pull request references OLS-2378 which is a valid jira issue.

Details

In response to this:

Description

This PR introduces Generic Provider Configuration support for LCore (Llama Stack) backend, enabling flexible LLM provider configuration beyond the predefined types.

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up dependent library

Related Tickets & Documents

• Related Issue # OLS-2378
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.

  • Configured OLS to use LCore as backend, as changes will not work with appserver backend.
  • Applied a valid config using remote:: openai as provider type.
  • Verified llama stack configmap generation and validation rules manually.

• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@sriroopar: This pull request references OLS-2378 which is a valid jira issue.

Details

In response to this:

Description

This PR introduces Generic Provider Configuration support for LCore (Llama Stack) backend, enabling flexible LLM provider configuration beyond the predefined types.

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up dependent library

Related Tickets & Documents

• Related Issue # OLS-2378
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.

  • Configured OLS to use LCore as backend, as changes will not work with appserver backend.
  • Applied a valid config using remote:: openai as provider type.
  • Verified llama stack configmap generation and validation rules manually.

• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign raptorsun for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@sriroopar: This pull request references OLS-2378 which is a valid jira issue.

Details

In response to this:

Description

This PR introduces Generic Provider Configuration support for LCore (Llama Stack) backend, enabling flexible LLM provider configuration beyond the predefined types.

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up dependent library

Related Tickets & Documents

• Related Issue # OLS-2378
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.

  • Configured OLS to use LCore as backend, as changes will not work with appserver backend.
  • Applied a valid config using remote:: openai as provider type.
  • Verified llama stack configmap generation and validation rules manually.
  • Checked liveliness of endpoint with openai provider and passed a query and verified that the response is valid.
  • Also verified with an invalid provider type.

• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@sriroopar: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[raptorsun]

The logics looks good :)
I have a doubt about having providers[].providerType beside providers[].type. This could be confusing for the users.
If the providers[].type is generic, we can put everything including the llamastack's providerType. the strucutre looks like

providers:
  - type: generic
    config: 
      provider_id: openai
      provider_type: remote::openai
      config:
        api_key: ${env.OPENAI_API_KEY}

moreover, the generic type is more llamaStackGeneric