diff --git a/blocked-edges/4.3.0-rc.0.yaml b/blocked-edges/4.3.0-rc.0.yaml
index bdcafe8da..0a24a299d 100644
--- a/blocked-edges/4.3.0-rc.0.yaml
+++ b/blocked-edges/4.3.0-rc.0.yaml
@@ -2,5 +2,6 @@ to: 4.3.0-rc.0
 from: .*
 # 4.2 -> 4.3 updates occasionally hit FailedCreatePodSandBox events, fixed in rc.3, but in neither 4.2.16 nor rc.0: https://bugzilla.redhat.com/show_bug.cgi?id=1787635
 # 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed degradation, fixed in 4.2.16 and rc.3, but in neither 4.2.13 nor rc.0: https://bugzilla.redhat.com/show_bug.cgi?id=1786993
+# 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed degradation, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149
 # 4.2 -> 4.3 updates occasionally hit RouteHealthDegraded degradation, fixed in rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1790704
-# 4.2.* -> 4.3.0-rc.0 Sometimes workloads on GCP are unreachable during 4.2.x to 4.3.0 upgrade sometimes: https://bugzilla.redhat.com/show_bug.cgi?id=1793635
+# 4.2 -> 4.3 updates on GCP occasionally have unreachable workloads: https://bugzilla.redhat.com/show_bug.cgi?id=1793635
diff --git a/blocked-edges/4.3.0-rc.3.yaml b/blocked-edges/4.3.0-rc.3.yaml
index 4c2d56fbb..76d3d9ff8 100644
--- a/blocked-edges/4.3.0-rc.3.yaml
+++ b/blocked-edges/4.3.0-rc.3.yaml
@@ -1,5 +1,6 @@
 to: 4.3.0-rc.3
 from: 4\.2\..*
 # 4.2 -> 4.3 updates occasionally hit FailedCreatePodSandBox events, fixed in rc.3, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1787635
+# 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed degradation, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149
 # 4.2 -> 4.3 updates occasionally hit RouteHealthDegraded degradation, fixed in rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1790704
-# 4.2.* -> 4.3.0-rc.3 Sometimes workloads on GCP are unreachable during 4.2.x to 4.3.0 upgrade sometimes: https://bugzilla.redhat.com/show_bug.cgi?id=1793635
+# 4.2 -> 4.3 updates on GCP occasionally have unreachable workloads: https://bugzilla.redhat.com/show_bug.cgi?id=1793635
diff --git a/blocked-edges/4.3.0.yaml b/blocked-edges/4.3.0.yaml
new file mode 100644
index 000000000..273b434e0
--- /dev/null
+++ b/blocked-edges/4.3.0.yaml
@@ -0,0 +1,4 @@
+to: 4.3.0
+from: 4\.2\..*
+# 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149
+# 4.2 -> 4.3 updates on GCP occasionally have unreachable workloads: https://bugzilla.redhat.com/show_bug.cgi?id=1793635
diff --git a/blocked-edges/4.3.1.yaml b/blocked-edges/4.3.1.yaml
index 6b2ede705..c203b4dc1 100644
--- a/blocked-edges/4.3.1.yaml
+++ b/blocked-edges/4.3.1.yaml
@@ -1,3 +1,4 @@
 to: 4.3.1
 from: 4\.2\.18
 # 4.2.18 is baked into 4.3.1 as a recommended update source, but we don't have a 4.2.18 release yet.  Block until we have a release, to avoid accidentally adding 4.2.18 -> 4.3.1 to channels if 4.2.18 ends up being a dud.
+# 4.2 -> 4.3 updates on GCP occasionally have unreachable workloads: https://bugzilla.redhat.com/show_bug.cgi?id=1793635
diff --git a/channels/candidate-4.3.yaml b/channels/candidate-4.3.yaml
index f5fad4e9f..cc8c86386 100644
--- a/channels/candidate-4.3.yaml
+++ b/channels/candidate-4.3.yaml
@@ -1,7 +1,7 @@
 name: candidate-4.3
 versions:
 # until s390 is released on 4.3 we may not want to include it in 4.3 channels
-- 4.2.16+amd64
+# 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149
 # not 4.2.17 because we had a long quiet time after 4.2.16 with no releases
 - 4.2.18+amd64
 - 4.2.19+amd64
diff --git a/channels/fast-4.3.yaml b/channels/fast-4.3.yaml
index 6c5eb389a..d45cc41eb 100644
--- a/channels/fast-4.3.yaml
+++ b/channels/fast-4.3.yaml
@@ -1,7 +1,7 @@
 name: fast-4.3
 versions:
 # until s390 is released on 4.3 we may not want to include it in 4.3 channels
-- 4.2.16+amd64
+# 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149
 # not 4.2.17 because we had a long quiet time after 4.2.16 with no releases
 - 4.2.18+amd64
 - 4.3.0
diff --git a/channels/stable-4.3.yaml b/channels/stable-4.3.yaml
index 0b4fdf134..8d9079fff 100644
--- a/channels/stable-4.3.yaml
+++ b/channels/stable-4.3.yaml
@@ -1,6 +1,7 @@
 name: stable-4.3
 versions:
 # until s390 is released on 4.3 we may not want to include it in 4.3 channels
+# 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149
 # not 4.2.17 because we had a long quiet time after 4.2.16 with no releases
 - 4.3.0
 - 4.3.1