Skip to content

Commit add3cd7

Browse files
authored
Add a "coming soon" to main doc page (#1501)
* wip * address review comments
1 parent 91a8c1c commit add3cd7

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

docs-source/content/_index.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,35 @@ Oracle is finding ways for organizations using WebLogic Server to run important
1717
The fastest way to experience the operator is to follow the [Quick Start guide]({{< relref "/quickstart/_index.md" >}}), or you can peruse our [documentation]({{< relref "/userguide/_index.md" >}}), read our [blogs](https://blogs.oracle.com/weblogicserver/how-to-weblogic-server-on-kubernetes), or try out the [samples]({{< relref "/samples/_index.md" >}}).
1818

1919
***
20+
##### Current release
21+
2022
The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 2.5.0.
2123
This release was published on February 26, 2020.
24+
25+
##### Preview of next planned release
26+
27+
The next planned release is 3.0.0-rc1 (release candidate). This release candidate will
28+
be suitable for use by early adopters who wish to test 3.0.0 features and provide
29+
feedback.
30+
31+
This release is planned for April 2020, subject to change.
32+
33+
The planned feature changes in 3.0.0-rc1 are:
34+
35+
* Introduction of a new "Model In Image" feature which allows you to have a domain
36+
created at pod startup time from a WebLogic Deploy Tool model and archive.
37+
This supports user-requested use cases like creating multiple domains from
38+
the same model and automated updating of the domain based on model changes.
39+
The operator automates management of the domain encryption keys to ensure
40+
that they are not changed during domain updates.
41+
* Support for running the operator on Kubernetes 1.16, 1.17 and 1.18.
42+
* Deprecation and removal of support for running the operator on Kubernetes 1.13
43+
and earlier versions.
44+
* Deprecation and removal of support for Helm 2.x. Helm 2.x uses the "tiller" pod
45+
which needs to run with elevated privileges (`cluster-admin` or very close to that)
46+
and which could be a vector for a privilege escalation attack. Helm 3.x removes
47+
tiller and does not create the same exposure.
48+
2249
***
2350

2451
{{% notice note %}}

0 commit comments

Comments
 (0)