openshift-docs
openshift-docs copied to clipboard
openshift
OBSDOCS-2041 COO 1.2.1 release notes
Version(s): 4.12+
Issue: OBSDOCS-2041
Link to docs preview: https://95426--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/cluster_observability_operator/cluster-observability-operator-release-notes.html
QE review:
- [ ] QE has approved this change.
Additional information:
🤖 Wed Jul 09 13:14:33 - Prow CI generated the docs preview:
https://95426--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/cluster_observability_operator/cluster-observability-operator-release-notes.html
I have created the changes, but I see now that the "Allow edits and access to secrets by maintainers" was accidentally not checked, so I cannot push the changes.
I have raised the changes here: https://github.com/openshift/openshift-docs/pull/95742/commits/2669916011db3a4ee5c270edf8595494b52ec492
so that @gabriel-rh can use that commit when he is back tomorrow.
@gabriel-rh @eromanova97 I added to the doc a known issue that we found while testing. Please check.
@gabriel-rh: 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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@gabriel-rh: new pull request created: #95895
In response to this:
/cherrypick enterprise-4.20
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.
@gabriel-rh: new pull request created: #95896
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.
@gabriel-rh: new pull request created: #95897
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.
@gabriel-rh: new pull request created: #95898
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.
@gabriel-rh: new pull request created: #95899
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.
@gabriel-rh: new pull request created: #95900
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.
@gabriel-rh: new pull request created: #95901
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.
@gabriel-rh: new pull request created: #95902
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.
@gabriel-rh: new pull request created: #95903
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.