-
Notifications
You must be signed in to change notification settings - Fork 5
Added recipe for elasticsearch. #27
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
base: main
Are you sure you want to change the base?
Conversation
| name: elastic | ||
| url: https://helm.elastic.co | ||
| type: helm | ||
| namespace: "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we set some default namespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay sure.
|
@ameydev don't we need to create |
|
Same for Kibana. Do we need to create |
|
As described in - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-kibana.html, we should also print a note containing - username, password, and link to dashboard |
- Recipe for ELC stack with eck-operator
| retry=0 | ||
| while true; | ||
| do | ||
| currentState=$(kubectl -n elastic-system get elasticsearches elasticsearch -o jsonpath='{.status.health}') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"elasticsearches" - typo?
No description provided.