Task Description (Required)

As described during the spike for https://issues.redhat.com/browse/DEVAI-137 the preferred approach is to ask the user to provide the name & the key of the secret that the api key is stored. Some key points:

• This implementation assumes that the user has already set the secret on their environment.
• The implementation should cover both openshift and openshift ai cases.
• The local deployment case is out of scope for this issue.
• The documentation of every updated template should include updated information regarding this feature.
• The first version of the feature supports the Bearer <token> authentication case.

Acceptance Criteria 

• The audio-to-text, chatbot, codegen, object-detection & rag templates support bearer authentication for BYO server cases.
• All templates have been thoroughly tested (for all model server cases).
• Necessary updates to documentation have been made to capture the functionality and the requirements of this feature.

If this requires Change Management, complete sections below: 

Change Request 

<Select which item is being changed>

[ ]  Add New Tokens

[ ]  Rotate Tokens

[ ]  Remove Tokens

[ ] Others: (specify)

  Environment

<Select which environment the change is being made on.  If both, open a separate issue so changes are tracked in each environment>

[ ]  Stage OR

[ ]  Prod

  Backout Plan

<State what steps are needed to roll back in case something goes wrong>

  Downtime

<Is there any downtime for these changes?  If so, for how long>

  Risk Level

<How risky is this change?>

  Testing

<How are changes verified?>

  Communication

<How are service owners or consumers notified of these changes?>