fix: Azure API key secret - key name

[nileger]

Description

This MR improves the documentation on using the AI Gateway with Azure by fixing the Azure API key secret's key name.

Change Type

/kind documentation

Changelog

NONE

Additional Notes

Authorization is hard-coded here

[nileger]

Doesn't exist in the latest v1.3.0 CRDs (see Backend).

[nileger]

I'll fix the failing check.

[artberger]

Hi @nileger thanks for opening this PR. I had a couple questions.

• Is api-key not supported? I thought both methods could work for Azure. In which case, perhaps we just add Authorization as an example vs. removing api-key. Part of the purpose of this topic was to show a non-standard auth method that you want to override the default settings, hence the api-key example.
• For your comment about the authHeaderOverride removed in the Backend CRD in 1.3.0, I am wondering if that is the right resource? I see the field still in the CRD that you linked to, e.g. here. The Backend is a kgateway CR, but 1.3.0 would be Gateway API. Maybe I am misunderstanding something.

[nileger]

Hi @artberger,

this isn't about Azure support for either api-key or Authorization. This is about how kgatewayretrieves the value from theSecret`.

As mentioned above (see here), Authorization is hard-coded in the kgateway code, which is why a Secret with api-key: ... will never work since kgateway won't be able to get the value, resulting in a error message about not being able to read the secret value.

Need to double-check the part with the authHeaderOverride.