Bug 1901424 - Kibana pod gets created even if the replicas are set to 0 when deploying fluentd stand-alone
Summary: Kibana pod gets created even if the replicas are set to 0 when deploying flue...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Hui Kang
QA Contact: Anping Li
Rolfe Dlugy-Hegwer
URL:
Whiteboard: logging-exploration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-25 06:59 UTC by yhe
Modified: 2022-10-14 03:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Previously, when deploying Fluentd as a stand-alone, a Kibana pod was created even if the value of `replicas` was `0`. This happened because Kibana defaulted to `1` pod even when there were no Elasticsearch nodes. The current release fixes this. Now, a Kibana only defaults to `1` when there are one or more Elasticsearch nodes. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1901424[*BZ#1901424*])
Clone Of:
Environment:
Last Closed: 2021-02-24 11:22:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 827 0 None closed Bug 1901424: Skip setting kibana replicas to 1 with zero es node 2021-02-05 23:53:49 UTC
Red Hat Knowledge Base (Solution) 5922291 0 None None None 2021-04-01 08:21:44 UTC
Red Hat Product Errata RHBA-2021:0652 0 None None None 2021-02-24 11:23:08 UTC

Description yhe 2020-11-25 06:59:24 UTC 
Description of problem:
When deploying fluentd stand-alone, the kibana pod gets created even if the replicas are set to 0, and the kibana pod is not created only when the whole visualization section is not set in the Cluster Logging instance. By the way, the elasticsearch pod is not created as long as the nodeCount is set to 0, which is as expected.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create the following Cluster Logging instance

apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
  name: "instance" 
  namespace: "openshift-logging"
spec:
  collection:
    logs:
      fluentd:
        resources:
          limits:
            memory: 736Mi
          requests:
            cpu: 100m
            memory: 736Mi
      type: fluentd
  logStore:
    elasticsearch:
      nodeCount: 0
    type: elasticsearch
  managementState: Managed
  visualization:
    kibana:
      replicas: 0
    type: kibana

2. Check pods in openshift-logging namespaces

Actual results:
The kibana pod gets created

Expected results:
The kibana pod doesn't get created

Additional info:
Comment 1 yhe 2020-11-25 07:03:07 UTC 
The kibana pod is not created only when the whole visualization section is not set in the Cluster Logging instance, the example is shown below.

apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
  name: "instance" 
  namespace: "openshift-logging"
spec:
  collection:
    logs:
      fluentd:
        resources:
          limits:
            memory: 736Mi
          requests:
            cpu: 100m
            memory: 736Mi
      type: fluentd
  logStore:
    elasticsearch:
      nodeCount: 0
    type: elasticsearch
  managementState: Managed
Comment 4 Anping Li 2020-12-21 02:54:30 UTC 
verified on clusterlogging.4.7.0-202012190243.p0. When kibana is 0 in clusterlogging/instance, the  kibana is 0 too in kibana CR.

  spec:
    managementState: Managed
    proxy:
      resources:
        limits:
          memory: 256Mi
        requests:
          cpu: 100m
          memory: 256Mi
    replicas: 0
    resources:
      limits:
        memory: 736Mi
      requests:
        cpu: 100m
        memory: 736Mi
Comment 10 errata-xmlrpc 2021-02-24 11:22:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Errata Advisory for Openshift Logging 5.0.0), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:0652
Note You need to log in before you can comment on or make changes to this bug.