-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.16.z
-
None
-
1
-
NE Sprint 260, NE Sprint 261, NE Sprint 262
-
3
-
Rejected
-
False
-
Description of problem :
I have noticed that in external DNS operator documentation, the wapiVersion present is "2.3.1" which is pretty old as there are multiple versions updated after that.
Then, after doing some R&D on this with the engineering team on the Slack thread[0], we found the NIOS 8.6.2 release notes which states the following about the WAPI versions support :
This NIOS release supports the following WAPI versions: 1.0, 1.1, 1.2, 1.2.1, 1.3, 1.4, 1.4.1, 1.4.2, 1.5, 1.6, 1.6.1, 1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 2.0, 2.1, 2.1.1, 2.1.2, 2.2, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4, 2.5, 2.6, 2.6.1, 2.7, 2.7.1, 2.7.2, 2.7.3, 2.8, 2.9, 2.9.1, 2.9.5, 2.9.7, 2.10, 2.10.1, 2.10.2, 2.10.3, 2.10.5, 2.11, 2.12, 2.12.1, and 2.12.2. - Unless explicitly stated in the release notes, previously available WAPI versions are intended to remain accessible and operative with later versions. - The planned deprecation of a given version of the WAPI will normally be announced in the release notes at least one year in advance. Upon deprecation, the announced WAPI version and all prior versions will no longer be supported in subsequent releases.
Also, we raised a test PR[1] with 2.9.1 as the default version for tests, and it passed all the e2e tests. So, 2.9.1 seems to be working fine with our Infoblox instance.
So, we need to update the latest wapiVersions in our product documentation[2] :
[1] https://github.com/openshift/external-dns-operator/pull/229
