-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RHDEVDOCS-5627: Adds missing 4.15 release note for builds #73708
Conversation
@opayne1: This pull request references RHDEVDOCS-5627 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
🤖 Tue Apr 30 18:29:06 - Prow CI generated the docs preview: |
@opayne1: This pull request references RHDEVDOCS-5627 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
@@ -184,6 +184,7 @@ This release introduces the following updates to the *Administrator* perspective | |||
|
|||
* Enable and disable the tailing to Pod log viewer to minimize load time. | |||
* View recommended values for `VerticalPodAutoscaler` on the *Deployment* page. | |||
* Opt-out of `BuildConfig` and `DeploymentConfigs` when a cluster does not have v1 builds. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think I fully understand this.
Are we asking users to disable BuildConfig
and DeploymentConfigs
if the cluster lacks support for builds for Red Hat OpenShift 1.0?
Is "v1 builds" how we officially refer to it? Sorry, can't seem to find an example in the docs. I probably missed something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly I am not really sure I understand this completely either @joaedwar can you help weigh in on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah @opayne1 I think I will ask/follow up with eng about this when they are back online. Would you have a screenshot of this handy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I think from the we should probably us enable or disable rather than opt-out , but I'll check if that is the case in the IBM style guide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joaedwar I just added a few updates to this. I am still not 100% on it. I do not have a screenshot on it at the moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @opayne1. That seems clear . I am just checking with QE to see what they say. Thank you for working on this :)
@@ -184,6 +184,7 @@ This release introduces the following updates to the *Administrator* perspective | |||
|
|||
* Enable and disable the tailing to Pod log viewer to minimize load time. | |||
* View recommended values for `VerticalPodAutoscaler` on the *Deployment* page. | |||
* Disable `BuildConfig` and `DeploymentConfigs` when a cluster does not have a `build.openshift.io/v1` API version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DeploymentConfig is a separate API, controlled by a separate cluster capability (DeploymentConfig
). If DeploymentConfig web console components are removed simply because the build.openshift.io
API group is not present, this is a bug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for reviewing @adambkaplan. So should this be added as a known issue, instead? I am not sure why we should disable these components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adambkaplan Just to elaborate the issue, we observed that when there is no build.openshift.io/v1` API version in the cluster, the DeployConfig does not work properly. We did a small spike to see that although the ReplicationController for the DC is getting created, still DC is not starting the pods. This hinted some underlining connection b/w the BC and DC.
But surely it may also be a bug. It would be great if we can ask someone from the respective team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But surely it may also be a bug. It would be great if we can ask someone from the respective team.
This is absolutely a bug. Potentially related to (or fixed by) OCPBUGS-22956
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like someone wrote up text for that bug, but it didn't make it into the release notes. I have reached out to the writer working in this area for more information.
I will most likely update this PR with a note for OCPBUGS-22956 in the bug fixes section of the release notes based on what I find out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to include the bug fix.
/assign @Lucifergene Avik is the owner of the respective epic, ODC-7352 |
LGTM |
1 similar comment
LGTM |
Hi @sferich888 and @xltian! This PR adds a bug to the release notes that was missed when batching in bugs to the 4.15 release. Could you provide an ack for change management? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/lgtm With that said we don't use ConfigObserver anywhere in our docs; but in this location (or update) so it may not be something customer understand or can parse if they read this update. In short it may be better to explain that the ConfigObserver is the CVO. |
New changes are detected. LGTM label has been removed. |
lgtm |
/remove-label peer-review-needed /label peer-review-in-progress |
Hi @opayne1 . WOuld you be OK to tick the QE Approved box? I think QE approved the PR? Also, is a CM needed for this? The OCP Docs Manual is not very clear. The Peer-review checklist states: |
@opayne1: This pull request references RHDEVDOCS-5627 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
/remove-label peer-review-in-progress /label peer-review-done |
@opayne1: 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/test-infra repository. I understand the commands that are listed here. |
Adds missing 4.15 release note for builds
Version(s):
4.15
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-5627
Link to docs preview:
https://73708--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-15-release-notes#ocp-4-15-administrator-perspective
QE review:
Additional information:
This will need change management
@invincibleJai @jerolimov @Preeticp @joaedwar