Unable to launch a Kibana CR instance using latest ElasticSearch operator, Steps needed about elasticsearch-operator HOT 12 CLOSED

Could you paste the log from the elasticsearch-operator? Thanks.

from elasticsearch-operator.

hello, thanks for ur response. we dont see any elastic-search operator pod in this xyz namespace
Rather there is one in the openshift-operators-redhat namespace

from elasticsearch-operator.

Below is ElasticInstance:

apiVersion: logging.openshift.io/v1
kind: Elasticsearch
metadata:
  name: elasticsearch
  namespace: xyz
spec:
  managementState: Managed
  nodeSpec:
    image: >-
      registry.redhat.io/openshift4/ose-logging-elasticsearch6@sha256:2c156f7e8896011e7eac8c58e661d3173ff8079d0b3f16045b1ac9cc68f4496f
    resources:
      limits:
        memory: 1Gi
      requests:
        memory: 512Mi
  nodes:
    - nodeCount: 1
      roles:
        - client
        - data
        - master
  redundancyPolicy: ZeroRedundancy

from elasticsearch-operator.

Is there any example or steps documented that can be referred to create ElasticInstance and Kibana CR instances, as I suspect we could be missing something

from elasticsearch-operator.

hello, thanks for ur response. we dont see any elastic-search operator pod in this xyz namespace
Rather there is one in the openshift-operators-redhat namespace

Yes, this is one I am referring to.

• The example you used only launches the elasticsearch instance, which is the expected. For kibana, the example is located at:

  elasticsearch-operator/test/e2e-olm/utils.go

  Line 263 in 5dd0f4f

  return &loggingv1.Kibana{

from elasticsearch-operator.

@Abu0108 do you have the cluster logging operator installed as well? we recommend using that if you are going to be deploying elasticsearch for logging

from elasticsearch-operator.

hello, thanks for ur response. we dont see any elastic-search operator pod in this xyz namespace
Rather there is one in the openshift-operators-redhat namespace

Yes, this is one I am referring to.

• The example you used only launches the elasticsearch instance, which is the expected. For kibana, the example is located at:

  elasticsearch-operator/test/e2e-olm/utils.go

  Line 263 in 5dd0f4f

  return &loggingv1.Kibana{

Thanks.. We did try launching Kibana Instance separately but we dont see anything happening.
No resources created at all.

apiVersion: logging.openshift.io/v1
kind: Kibana
metadata:
  name: kibana
  namespace: xyz
spec:
  replicas: 1
  resources:
    limits:
      memory: 512Mi
    requests:
      memory: 512Mi
  managementState: Managed
  nodeSelector: {}

from elasticsearch-operator.

@Abu0108 do you have the cluster logging operator installed as well? we recommend using that if you are going to be deploying elasticsearch for logging

We dont have CLO installed in this namespace as shown in above screen shots, our objective is to use this elastic and kibana instance for tracing.

It would be very helpful if you could point us few CR instance examples that can provision Elastic and Kibana both pods.

Thanks in advance

from elasticsearch-operator.

@ewolinetz @huikang Can you have a look and help here? Thanks.

from elasticsearch-operator.

@abu-2020-ghub did you check the elasticsearch operator logs? it is likely that you do not have the required secrets for kibana/kibana-proxy.

Normally CLO creates these so that all components can communicate and mutually trust one another. However, if you are looking to do this strictly in a dev manner, you can use the make target deploy-example-secret, just ensure that your kibana and elasticsearch CRs are in the namespace openshift-logging

from elasticsearch-operator.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from elasticsearch-operator.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from elasticsearch-operator.