apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62179" uid: cd7ea2fd-176d-4f04-a5b5-439466538d9d spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T04:17:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.164918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 881.077µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 1.202344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 2.047553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 1.585151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 864.491µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:47:40Z" - latency: 1.49779ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:46:40Z" - latency: 1.485251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:45:40Z" - latency: 910.913µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:44:40Z" - latency: 1.157318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:43:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62181" uid: e6f5b802-5697-454d-8ef7-ef28a6ef39c3 spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T04:16:40Z" message: 'load-balancer-api-external: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.0611ms message: 'load-balancer-api-external: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 8.452357ms message: 'load-balancer-api-external: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:52:40Z" - latency: 3.456611ms message: 'load-balancer-api-external: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 9.874739ms message: 'load-balancer-api-external: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:51:40Z" - latency: 3.41278ms message: 'load-balancer-api-external: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 9.241353ms message: 'load-balancer-api-external: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:50:40Z" - latency: 4.677361ms message: 'load-balancer-api-external: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 10.1681ms message: 'load-balancer-api-external: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:49:40Z" - latency: 5.154187ms message: 'load-balancer-api-external: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 9.127753ms message: 'load-balancer-api-external: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:48:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62182" uid: bb8414a1-06da-488c-85ce-0b64995a25fe spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T04:16:40Z" message: 'load-balancer-api-internal: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.087919ms message: 'load-balancer-api-internal: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 8.507844ms message: 'load-balancer-api-internal: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:52:40Z" - latency: 3.443965ms message: 'load-balancer-api-internal: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 9.638375ms message: 'load-balancer-api-internal: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:51:40Z" - latency: 3.359757ms message: 'load-balancer-api-internal: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 9.365067ms message: 'load-balancer-api-internal: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:50:40Z" - latency: 4.679472ms message: 'load-balancer-api-internal: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 10.356296ms message: 'load-balancer-api-internal: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:49:40Z" - latency: 4.263544ms message: 'load-balancer-api-internal: tcp connection to a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 9.191891ms message: 'load-balancer-api-internal: resolved host name a489dba5ae86540fd84683b2bbf3f357-e2106f2ddf05a33a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T04:48:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-network-check-target-ip-10-0-128-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62175" uid: 05a2832c-52ad-49fe-ab94-d779b02098e9 spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T04:17:40Z" message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.364167ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 1.485795ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 984.092µs message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 2.328822ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 1.262207ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 748.695µs message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:47:40Z" - latency: 1.189093ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:46:40Z" - latency: 1.019063ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:45:40Z" - latency: 991.102µs message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:44:40Z" - latency: 1.611432ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:43:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-network-check-target-ip-10-0-129-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62177" uid: 30164d57-51e3-4932-ba85-434d33c1d243 spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T04:17:40Z" message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.074908ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 2.381547ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 2.35906ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 2.490988ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 2.363299ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 1.844039ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:47:40Z" - latency: 2.186034ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:46:40Z" - latency: 2.181061ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:45:40Z" - latency: 2.037226ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:44:40Z" - latency: 2.167795ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:43:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-network-check-target-ip-10-0-136-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62176" uid: 8d46b19d-c969-4dda-a9c3-c4363df0e41d spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T04:17:40Z" message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.971272ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 1.928873ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 2.351726ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 2.914739ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 2.196766ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 2.051268ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:47:40Z" - latency: 2.161706ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:46:40Z" - latency: 2.168003ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:45:40Z" - latency: 2.108825ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:44:40Z" - latency: 2.270078ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:43:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T04:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-222-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-222.ec2.internal uid: e4e2d883-741a-4dd8-acba-94e6201da2aa resourceVersion: "62178" uid: 6f1e7e31-8cbe-47d1-9585-f1198ff783b3 spec: sourcePod: network-check-source-869dcfcdcd-vm2mz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T04:16:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.859µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:52:40Z" - latency: 1.614074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T04:52:40Z" - latency: 968.522µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:51:40Z" - latency: 2.185894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T04:51:40Z" - latency: 1.228093ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:50:40Z" - latency: 2.029576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T04:50:40Z" - latency: 958.007µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:49:40Z" - latency: 3.233291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T04:49:40Z" - latency: 1.227266ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T04:48:40Z" - latency: 1.919529ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T04:48:40Z" kind: List metadata: resourceVersion: ""