openshift
Update list of all supported wapiVersions in External DNS Operator Documentation
Update list of all supported wapiVersions in external dns operator documentations
https://issues.redhat.com/browse/OSDOCS-12220
Version(s):
4.16+
Issue:
https://issues.redhat.com/browse/OSDOCS-12220
Link to docs preview:
https://83270--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/external_dns_operator/nw-creating-dns-records-on-infoblox.html
QE review:
- [ ] QE has approved this change.
Additional information:
Currently in External DNS operator documentation, the wapiVersion present is "2.3.1" which is quite old as there are multiple new versions updated after that.
- Here are the list of currently supported wapiVersions: 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.
- Unless explicitly stated in the release notes, previously available WAPI versions are intended to remain accessible and operative with later versions.
Also, we raised a test PR[1] with the latest wapiVersion "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 list of all supported wapiVersions in our product documentation[2] to avoid the confusion : [1] openshift/external-dns-operator#229 [2] https://docs.openshift.com/container-platform/4.16/networking/external_dns_operator/nw-creating-dns-records-on-infoblox.html
@ankhande: Can not set label peer-review-in-progress: Must be member in one of these teams: [team-red-hat]
In response to this:
/label peer-review-in-progress
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-sigs/prow repository.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @ankhande. Thanks for your PR.
I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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-sigs/prow repository.
🤖 Fri Oct 25 02:02:23 - Prow CI generated the docs preview:
https://83270--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/external_dns_operator/nw-creating-dns-records-on-infoblox.html
@ankhande: Can not set label merge-review-needed: Must be member in one of these teams: [team-red-hat]
In response to this:
/label merge-review-needed
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-sigs/prow repository.
Hi, this did not have a peer review by the OpenShift docs team. It needs one before it can be merged. I will do that peer review.
@ankhande: 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-sigs/prow repository. I understand the commands that are listed here.
You need to squash the commits before we can merge this PR.
/remove-label merge-review-needed /remove-label merge-review-in-progress
The branch/enterprise-4.19 label has been added to this PR.
This is because your PR targets the main branch and is labeled for enterprise-4.18. And any PR going into main must also target the latest version branch (enterprise-4.19).
If the update in your PR does NOT apply to version 4.19 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
The branch/enterprise-4.20 label has been added to this PR.
This is because your PR targets the main branch and is labeled for enterprise-4.19. And any PR going into main must also target the latest version branch (enterprise-4.20).
If the update in your PR does NOT apply to version 4.20 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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-sigs/prow repository.