Skip to content

Conversation

@prithvipatil97
Copy link
Contributor

@prithvipatil97 prithvipatil97 commented Oct 29, 2025

Here is the current look:

  1. Create a secret with the credentials to access the object storage. For example, create a secret to access Amazon Web Services (AWS) s3.
apiVersion: v1
kind: Secret
metadata:
  name: logging-loki-s3  1 
  namespace: openshift-logging
stringData:  2 
  access_key_id: <access_key_id>
  access_key_secret: <access_secret>
  bucketnames: s3-bucket-name
  endpoint: https://s3.eu-central-1.amazonaws.com
  region: eu-central-1
  • access_key_secret value is wrongly mentioned.
  • It needs to be corrected. The correct value is secret_access_key
  • Also change the s3-bucket-name to <s3_bucket_name>.

Here is the updated look:

  1. Create a secret with the credentials to access the object storage. For example, create a secret to access Amazon Web Services (AWS) s3.
apiVersion: v1
kind: Secret
metadata:
  name: logging-loki-s3  1 
  namespace: openshift-logging
stringData:  2 
  access_key_id: <access_key_id>
  access_key_secret: <secret_access_key>
  bucketnames: <s3_bucket_name>
  endpoint: https://s3.eu-central-1.amazonaws.com
  region: eu-central-1

Version(s):

Logging 6.4, Logging 6.3, Logging 6.2, Logging 6.1, Logging 6.0

Issue:

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

Link to docs preview:

https://101390--ocpdocs-pr.netlify.app/openshift-logging/latest/installing/installing-logging.html

QE review:

  • QE has approved this change.

Additional information:

AWS secret code needs to be corrected
Here is the documentation link:
https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.3/html/installing_logging/installing-logging#install-loki-operator-cli_installing-logging:~:text=Create%20a%20secret%20with%20the%20credentials%20to%20access%20the%20object%20storage.%20For%20example%2C%20create%20a%20secret%20to%20access%20Amazon%20Web%20Services%20(AWS)%20s3. 
Here is the current look:
9. Create a secret with the credentials to access the object storage. For example, create a secret to access Amazon Web Services (AWS) s3.

apiVersion: v1
kind: Secret
metadata:
  name: logging-loki-s3  1 
  namespace: openshift-logging
stringData:  2 
  access_key_id: <access_key_id>
  access_key_secret: <access_secret>
  bucketnames: s3-bucket-name
  endpoint: https://s3.eu-central-1.amazonaws.com
  region: eu-central-1 
`access_key_secret` value is wrongly mentioned.
It needs to be corrected. The correct value is `access_key_secret`
Here is the updated look:
9. Create a secret with the credentials to access the object storage. For example, create a secret to access Amazon Web Services (AWS) s3.

apiVersion: v1
kind: Secret
metadata:
  name: logging-loki-s3  1 
  namespace: openshift-logging
stringData:  2 
  access_key_id: <access_key_id>
  access_key_secret: <secret_access_key>
  bucketnames: <s3_bucket_name>
  endpoint: https://s3.eu-central-1.amazonaws.com
  region: eu-central-1
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 29, 2025
@ocpdocs-previewbot
Copy link

🤖 Wed Oct 29 22:49:57 - Prow CI generated the docs preview:

https://101390--ocpdocs-pr.netlify.app/openshift-logging/latest/installing/installing-logging.html

@openshift-ci
Copy link

openshift-ci bot commented Oct 29, 2025

@prithvipatil97: all tests passed!

Full PR test history. Your PR dashboard.

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

Hello Team,
I need QE approval for this change.

All checks have passed, and I have reviewed the PR with the peer review checklist.

@anpingli , @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

@anpingli
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 30, 2025
@prithvipatil97
Copy link
Contributor Author

Hello Anping Li,
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 Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm Indicates that a PR is ready to be merged. merge-review-needed Signifies that the merge review team needs to review this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants