-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Update list of all supported wapiVersions in External DNS Operator Documentation #83223
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
Conversation
MCO114: tlsSecurityProfile parameter for MCO & MCS
…ubleshooting [OSDOCS-11001]: Moving HCP troubleshooting docs to OCP
…ubleshooting Fixing errors in HCP troubleshooting file
Update backup-etcd.adoc Update backup-etcd.adoc Update backup-etcd.adoc
OSDOCS-11382: Renaming the user in ANP
TELCODOCS#1877: Enabling the SR-IOV network metrics exporter
TELCODOCS#1889: Size info for LVMS
OSDOCS-11819: Move bare metal config docs to bare metal install section
OSDOCS-10767: Re-work first half of the "Getting Started with ROSA" Tutorials to be HCP specific
Review updates further updates for Jack Lisa's comments
HCIDOCS-376: Fix indents in networkConfig stanza, install-config.yml (IPI)
HCIDOCS-376: Fix indents in networkConfig stanza, install-config.yml (IPI)
…-WID-for-OLM-CCO OSDOCS-11734: GCP Workload ID OLM stub and related updates
…grate OSDOCS#11000: Migrating and modularizing HCP requirements from RHACM to OCP
…e-versions OSDOCS-12013 specified z-stream version to scale to 250 nodes in HCP
OSDOCS#11979: Add CRD upgrade safety for OLMv1
Adds note that MEG and egress are incompatible
OSDOCS-12018: fix FIPS link and correct attributes
…cept TELCODOCS-1861: Add concept module for introducing IBGU
RHDEVDOCS-5840 - Change redirects
TELCODOCS-1841: Configuring disk encryption with PCR protection
…32774 OCPBUGS-32774#updating Azure CLI version
[OCPBUGS-37806] Change RHEL links to new locations
CNV-45185: Issue in file virt/virtual_machines/advanced_vm_management/virt-high-availability-for-vms.adoc
…5-nodes [OSDOCS-11570]: Adding docs about 4 and 5 node architecture
CNV#46303: [enterprise-4.16] Issue in file virt/virtual_machines/creating_vms_custom/virt-creating-vms-from-container-disks.adoc
…d_missing_router_port [enterprise-4.16+]: network-flow-matrix: add missing openshift-router port
…e with our infoblox instance
Update currently supported wapiVersions with external dns operator configuration
PR needs rebase. 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 @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 Once the patch is verified, the new status will be reflected by the 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. |
/label peer-review-needed |
@ankhande: Can not set label peer-review-needed: Must be member in one of these teams: [team-red-hat] In 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-sigs/prow repository. |
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:
QE review:
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 "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