-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Added 4.2 release notes #16410
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
Added 4.2 release notes #16410
Conversation
74765d7 to
77c1d2b
Compare
77c1d2b to
06cab55
Compare
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.
4.2 introduces both disconnected installs and proxy supported installs
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.
though this was tech preview in 4.2.. cc @knewcomerRH
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.
Not even tech preview. Please remove any reference to FIPS mode. 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.
deprecated in 4.2? cc @jwforres (I don't know where this landed)
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.
(same for the 2 brokers below)
|
Storage changes:
|
|
FIPS mode is not supported in 4.2 and should be removed from the release
notes. (While RHCOS can be configured in FIPS mode, OCP crashes when
running on OCP in FIPS mode.)
Kirsten
Kirsten Newcomer
OpenShift Product Management
[email protected]
+1 978-392-8114 (office)
+1 781-710-2184 (mobile)
…On Mon, Sep 9, 2019 at 4:47 PM Christian Huffman ***@***.***> wrote:
Storage changes:
- In 4.1 release notes EFS was incorrectly marked as general
availability. This is being included as a technology preview feature in 4.2.
- Persistent volume snapshots are being deprecated in OCP 4.2.
- Persistent volumes using the Local Storage Operator is being
introduced in OCP 4.2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16410?email_source=notifications&email_token=AGCUYWDCNS5VSAWHEQ3YOFTQI2Y53A5CNFSM4IQKRWSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6I7SAQ#issuecomment-529660162>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGCUYWBMHHTSCVWPDZURAFLQI2Y53ANCNFSM4IQKRWSA>
.
|
06cab55 to
8e2cd3e
Compare
f46a8b5 to
c22e4f2
Compare
|
The preview will be available shortly at: |
c22e4f2 to
3e50d93
Compare
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.
{product-version} here and at other places.
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.
We need to add header formatting here - please and thank you!
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.
Is this supposed to be a header?
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.
Suggested replacement for this section:
When creating an IngressController on cloud platforms, the IngressController is
published by a public cloud load balancer by default.
Users can now publish IngressControllers with internal cloud load balancers. For example:
apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
namespace: openshift-ingress-operator
name: internal
spec:
endpointPublishingStrategy:
type: LoadBalancerService
loadBalancer:
scope: Internal
See the link:https://kubernetes.io/docs/concepts/services-networking/#internal-load-balancer.[Kubernetes Services documentation]
for implementation details.
Note that once set, .spec.endpointPublishingStrategy.loadBalancer.scope cannot
be changed. To change the scope, delete and recreate the IngressController.
The default IngressController can be made internal by deleting and recreating
it.
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.
cc @openshift/sig-network-edge
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.
Since this is release notes, I think we should move the details and example to product document (a new topic in https://docs.openshift.com/container-platform/4.2/networking/ingress-operator.html), and here just provide the link to it like:
See xref:.. for more information.
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.
So I've created #16963 for this content.
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.
@zvonkok can you review the above statements for GPU enablement?
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.
@zvonkok @ahardin-rh should SRO documentation be included in product docs? It is a community operator at this point, right?
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.
@ashishkamra I will pull it out for now. 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.
iSCSi -> iSCSI
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 guess the RHHI.next section may need to be removed after the recent announcements
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.
@gabemontero do we have a note elsewhere about the restrictions on builds in disconnected envs? (sounds like the restriction is "they won't work" at this point since there is no way for the user to get the creds to be correct for the mirror)
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.
nm, found the note/limitation at the bottom.
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.
is moved to the dev perspective, right @spadgett? should probably say where it was moved to.
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.
Yes, it's moved to the Developer perspective.
Developer -> Add+ -> From Catalog
c3791ff to
72f5e5e
Compare
84a9a84 to
4b529d5
Compare
c6dea59 to
cf481b2
Compare
656efe1 to
9927ce2
Compare
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 think that we need to add
brokertemplateinstance.template.openshift.io
This is only added when template-service-broker is installed.
@bparees can you ack that this is correct and that we should add it here?
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.
actually it looks like brokertemplateinstance is served out of the openshift apiserver, so i guess it'll still be present (but utterly useless w/ no TSB).
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.
Should we remove this type in 4.4 as well?
9927ce2 to
9daed32
Compare
|
I believe I addressed all feedback to date; I am merging this now and we can continue to iterate in separate PRs. |
|
/cherrypick enterprise-4.2 |
|
@ahardin-rh: new pull request created: #16972 DetailsIn 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 kubernetes/test-infra repository. |
|
@ahardin-rh new edit suggestion in #17174 |
Preview Build: http://file.rdu.redhat.com/~ahardin/09232019/OCP-4-2-release-notes/release_notes/ocp-4-2-release-notes.html