Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passing mimir endpont and auth details in keda autoscaling #9616

Closed
snyaik opened this issue Oct 15, 2024 · 1 comment
Closed

Passing mimir endpont and auth details in keda autoscaling #9616

snyaik opened this issue Oct 15, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@snyaik
Copy link

snyaik commented Oct 15, 2024

Hi Everyone,

I am trying to implement keda for miimir components.
Keda is working fine when the prometheusAddress and customHeaders fields are left blank.
I want to pass the mimir endpoint along with the auth details to kedaAutoscaling block.

When I am passing the mimir endpoint in prometheus address it fails with 401 unauthorised error.

There is not much info available on how to pass auth details in kedaAutoscaling block.
Is there any specific format to be followed in passing auth details in customheaders.
I have gone through keda documentation where I can see how to pass auth details but how to translate that into mimir values?

Expected behaviour: keda to work without metamonitoring block and by passing mimir endpoint in prometheus address.

@narqo
Copy link
Contributor

narqo commented Oct 15, 2024

Looking at the list of remaining work for stabilising autoscaling, this might not be supported yet. Refer to #7368:

Currently basic auth and extra headers are ignored.

I suggest moving the issue there (or feel free to reopen this one providing more details for your particular scenario).

@narqo narqo closed this as completed Oct 15, 2024
@narqo narqo added the duplicate This issue or pull request already exists label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants