Skip to content

Update cluster-logging-kibana-scaling.adoc#89957

Merged
xenolinux merged 1 commit intoopenshift:mainfrom
prithvipatil97:patch-36
Mar 11, 2025
Merged

Update cluster-logging-kibana-scaling.adoc#89957
xenolinux merged 1 commit intoopenshift:mainfrom
prithvipatil97:patch-36

Conversation

@prithvipatil97
Copy link
Contributor

@prithvipatil97 prithvipatil97 commented Mar 10, 2025

=======================================

  • namespace name is missing from the command.
  • same command is mentioned twice in the second block. Which is not required and hence needs to be removed.
  • "namespace: openshift-logging" field is missing under metadata section.
  • 2 extra spaces under spec.visulization, it will not cause any effect. But it needs to be with correct indentation.

=======================================

=======================================
Reason:

  1. Suppose the user is not a part of openshift-logging project, and he tries to run this command then this command will not work.
  2. If the credentials are shared, and two people are using the same cluster at the same time, then, the second person could change to work in a different namespace.

=======================================

Updated documentation will look like the following:

  1. Edit the ClusterLogging custom resource (CR) in the openshift-logging project:
$ oc -n openshift-logging edit ClusterLogging instance 
apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
  name: "instance"
  namespace: openshift-logging
....

spec:
  visualization:
    type: "kibana"
    kibana:
      replicas: 1 

Version(s):

RHOCP-4.18, RHOCP-4.17, RHOCP-4.16, RHOCP-4.15, RHOCP-4.14, RHOCP-4.13, RHOCP-4.12

Issue:

https://issues.redhat.com/browse/OBSDOCS-1756

Link to docs preview:

https://89957--ocpdocs-pr.netlify.app/openshift-rosa/latest/observability/logging/log_visualization/logging-kibana.html

QE review:

  • QE has approved this change.

Additional information:

- Incorrect configuration under scaling redundancy for the log visualizer nodes documentation

- Here is the documentation link:
https://docs.openshift.com/container-platform/4.16/observability/logging/log_visualization/logging-kibana.html#cluster-logging-kibana-scaling_logging-kibana

=============
- namespace name is missing from the command.
- same command is mentioned twice in the second block. Which is not required and hence needs to be removed.
- "namespace: openshift-logging" field is missing under `metadata` section.
- 2 extra spaces under `spec.visulization`, it will not cause any effect. But it needs to be with correct indentation.
===========
===========
Reason:

1. Suppose the user is not a part of openshift-logging project, and he tries to run this command then this command will not work.
2. If the credentials are shared, and two people are using the same cluster at the same time, then, the second person could change to work in a different namespace.
===============

Updated documentation will look like the following:

1. Edit the ClusterLogging custom resource (CR) in the openshift-logging project:

~~~
$ oc -n openshift-logging edit ClusterLogging instance
~~~
~~~
apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
  name: "instance"
  namespace: openshift-logging
....

spec:
  visualization:
    type: "kibana"
    kibana:
      replicas: 1 
~~~
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 10, 2025
@ocpdocs-previewbot
Copy link

@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2025

@prithvipatil97: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@prithvipatil97
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Mar 10, 2025
@mburke5678 mburke5678 added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Mar 11, 2025
@mburke5678
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 11, 2025
@mburke5678 mburke5678 added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Mar 11, 2025
@mburke5678 mburke5678 added this to the Continuous Release milestone Mar 11, 2025
@prithvipatil97
Copy link
Contributor Author

Hello @mburke5678 ,
Thank you very much for reviewing this PR and providing approval.

Yes, these changes needs to be merged from RHCOP 4.12 and +

Regards,
Prithviraj Patil

@prithvipatil97
Copy link
Contributor Author

Hello Team,
I need QE approval for this change.

All checks have passed and Peer review is also done.

@anpingli , @kabirbhartiRH , @QiaolingTang , It would be really helpful if someone could please take a look and provide QE approval for this change.

Thanks in advance.

Regards,
Prithviraj Patil

@QiaolingTang
Copy link

LGTM.

@prithvipatil97
Copy link
Contributor Author

Hello @QiaolingTang ,
Thank you very much for providing the QE approval for this change.

Regards,
Prithviraj Patil

@prithvipatil97
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 11, 2025
@xenolinux xenolinux added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Mar 11, 2025
Copy link
Contributor

@xenolinux xenolinux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM merging

@xenolinux xenolinux merged commit ebb7678 into openshift:main Mar 11, 2025
2 checks passed
@xenolinux xenolinux removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Mar 11, 2025
@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.19

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.18

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.17

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.16

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.15

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.14

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.13

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.12

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90029

Details

In response to this:

/cherrypick enterprise-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90030

Details

In response to this:

/cherrypick enterprise-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90031

Details

In response to this:

/cherrypick enterprise-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90032

Details

In response to this:

/cherrypick enterprise-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90033

Details

In response to this:

/cherrypick enterprise-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90034

Details

In response to this:

/cherrypick enterprise-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90035

Details

In response to this:

/cherrypick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #90036

Details

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 lgtm Indicates that a PR is ready to be merged. peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants