@Esakki just got back from my PTO. glad you got it working. did you use a different certs for ES and Kibana or do they use the same cert?
You can route search and ingest request to specific nodes via node affinity. I do that very thing via ElasticKonductor.
Esakki
October 12, 2023, 12:56pm
23
I raised different CSR for KIbana and elasticsearch erspectively and that resolved the issue.. and now all working..
The new requirement is to install ECK-CR IndexTemplate in my GKE on-prem k8s where I have my elasticsearch cluster..
I referred the below blogs/docs, I'm able to create the ECK-CR pod, and I created IndexTemplate yaml when I do kubectl create -f indextemplate.yaml, in my CR pod logs I can see that CR is unable to reach elasticsearch, and I'm getting 401 unauthorized error, I tried different ways but not working..
Note: My client don't want to create the indextemplate from Kibana (GUI) or using Elasticsearch API, they want it in a .yaml file... (From kibana GUI I'm able to create and using curl PUT cmd on the elastic API also working fine..
# Index Template (indextemplates.es.eck.github.com)
Representation of the Index template resource.
## Lifecycle
Index template lifecycle is simple - when the template is deleted
from K8s, it is also deleted from ES.
Create and Update are done using the same `PUT /_index_template` API.
See [Create or update index template API](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-template.html)
in official documentation.
## Fields
| Key | Type | Description |
|------------------------------------|--------|-------------------------------------------------------------------------------------------------|
| `metadata.name` | string | Name of the Index Template |
| `spec.targetInstance.name` | string | Name of the [Elasticsearch Instance](cr_elasticsearch_instance.md) to which this IndexTemplate will be deployed to |
| `spec.body` | string | Index template definition - same you would use when creating index template using ES REST API |
| `spec.dependencies.indexTemplates` | list | List of index templates that have to be present in ES cluster before index is created / updated |
show original
Esakki:
ent ways but not working..
Note: My client don't want to create the indextemplate from Kibana (GUI) or using Elasticsearch API, they want it in a .yaml file... (From kibana GUI I'm able to create and us
I'm not familiar with that CRD but it seems you need to spec.targetInstance.name based on the Elasticsearch Instance and Kibana Instance CRDs.
Esakki
October 13, 2023, 9:51am
25
@Sunile_Manjee thank you , let me try this.
Kind Regards,
Esakki
October 13, 2023, 1:24pm
26
@Sunile_Manjee I tried that also not working.
Esakki Regards,
This is a 3rd party CRD. since it is not working based on following the docs, I recommend you open a issue the author here: Issues · xco-sk/eck-custom-resources · GitHub
Esakki
October 17, 2023, 4:35am
28
@Sunile_Manjee Yeah, raised, and waiting for their response..
opened 01:54PM - 16 Oct 23 UTC
Hello Experts,
In our project we are using GKE Anthos On-Prem Kubernetes, wh… ere we have deployed ElasticSearch and Kibana version 8.9.1, and they are up and running without any problem..
1. I have separate DNS for Elasticsearch and Kibana, something like this, https://elasticsearch.uat.mydomain.com
https://kibana.uat.mydomain.com, and I have separate certs for these two URLs, and I have configured all required steps and everything is working.. (I haven't used ECK to install elastic and kibana, but I created .yaml files for those and created the deployments)
2. Now the next requirement is to install/deploy custom resources , I have followed the steps mentioned in this doc to deploy/install IndexTemplate but it's not working..
https://github.com/xco-sk/eck-custom-resources/blob/main/README.md
More Details,
Once I executed those two helm command in the given document, custom resource operator pod got created (and it's completely looks fine, I mean no pod restarts and no error logs) in the same K8s namespace where I have deployed elasticsearch and Kibana.. and in the values.yaml I have updated my elasticsearch and kibana URLs with correct certs and secrets details, after that I created the Elasticsearchinstance and Indextemplate yamls as per the doc, once I executed the Indextemplate.yaml file I can see that the CR operator pod started restarting, also I can see the pod logs with above attached 401 error.. I verified the secrets and URLs all are looks fine, but not sure why it's throwing 401..
and one more thing, normally when I do curl to my elastisearch url like this "curl https://elasticsearch.uat.mydomain.com" it will give unauthorized error, but when I pass with creds like this "curl **-u elastic:password** https://elasticsearch.uat.mydomain.com" then this working fine,, so I'm confused may be the secrets that I used is not taking or may be it's not properly updated to the URL?
Kindy do the needful, I'm struck in this issue for more than 4 days now.
Kind Regards,
Esakki
Is there any official doc that I can follow to achieve the same requirement?
I want to create custom resource to create Index-template(s) in my elasticsearch cluster.
Kind regards,
system
November 14, 2023, 4:36am
29
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.