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

Scaler support for ElasticSearch Service on Elastic Cloud #3785

Closed
rcbop opened this issue Oct 29, 2022 · 0 comments · Fixed by kedacore/keda-docs#966
Closed

Scaler support for ElasticSearch Service on Elastic Cloud #3785

rcbop opened this issue Oct 29, 2022 · 0 comments · Fixed by kedacore/keda-docs#966
Assignees
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@rcbop
Copy link
Contributor

rcbop commented Oct 29, 2022

Proposal

Support connection with ElasticSearch on Elastic Cloud by adding two new parameters cloudID and apiKey to be used in the go-elasticsearch client initialization:

cfg := elasticsearch.Config{
  CloudID: "my-cluster:dXMtZWFzdC0xLZC5pbyRjZWM2ZjI2MWE3NGJm...",
  APIKey:  "VnVhQ2ZHY0JDZGJrUW...",
}
  • These new parameters should be passed via Metadata or Auth sections.
  • The scaler should exit with error if an user attempt to provide both endpoint addresses and cloudID at the same time.

Use-Case

Enable usage of ElasticSearch Service on Elastic Cloud by using only cloudID and apiKey

Anything else?

This is the first step to build a new custom scaler.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant