Version 4.0.0

[hyder]

Hi everyone,

First of all, thank you to all our contributors and users. Your continued usage and interesting use cases have contributed to make this project better than when it started.

We want to give the community a bit of an update where we are heading. We have started working on version 4.0.0 of the terraform-oci-oke module and we would like to achieve a few things with version 4.0.0:

1. Terraform 1.0.0 support - take the opportunity to remove code that are either deprecated in the OCI provider or in Terraform itself
2. Improve the ability to introduce new features at a lower level, particularly in networking/vcn and bring it to the oke module
3. Improve reusability of this module
4. Standardize control variables

As you are aware, the VCN portion is currently handled inside the base module. However, every time we have a request that affects something at the VCN level, we need to create a new release for the vcn module, a new release for the base module that uses the new vcn release and then a new release for the OKE module. Similarly, new features or capabilities we want to introduce in either the bastion or operator modules, we have to go through the same lengthy process before they are surfaced in the oke module.

Secondly, there has been a number of requests from our users to reuse existing infrastructure e.g, VCN but they want to keep other capabilities like installing calico. In the current form, it is quite hard to meet those requirements.

To that end, we need to do the following:

1. Decouple the OKE module from the base module
2. Invoke the VCN, bastion and operator modules directly instead of the base module

Version 4.0.0 will therefore be a breaking change. Unfortunately, this also means that there is no practical upgrade path from 3.x to 4.x.

Next steps
If you're an existing user of 3.x, please carry on. We'll keep doing patchset releases for 3.x for another 6 months after the GA release of 4.0.0. However, at some point, in order to enjoy the new features and capabilities, you'll need to create a new cluster with the 4.x of this module and migrate your application workload to the new cluster.

We'll also start 4.0-beta releases soon. We would greatly appreciate if you could help us with testing and give us your feedback both on the above plans as well as the actual 4.0.0-betas.