apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "61537" uid: bffa1fb0-800d-4e9a-850d-51ccef21044e spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T12:22:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 1.262234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 1.30093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 1.025596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 1.318703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:46:41Z" - latency: 1.806759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:45:41Z" - latency: 1.304745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:44:41Z" - latency: 1.001474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:43:41Z" - latency: 1.015069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:42:41Z" - latency: 1.17719ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:41:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "62387" uid: 69568e33-55a5-416a-8ca9-0fcaddd44fce spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T12:21:41Z" message: 'load-balancer-api-external: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.742568ms message: 'load-balancer-api-external: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:51:41Z" - latency: 6.966638ms message: 'load-balancer-api-external: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:51:41Z" - latency: 5.907138ms message: 'load-balancer-api-external: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 7.596656ms message: 'load-balancer-api-external: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:50:41Z" - latency: 5.820419ms message: 'load-balancer-api-external: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 6.813214ms message: 'load-balancer-api-external: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:49:41Z" - latency: 5.188764ms message: 'load-balancer-api-external: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 9.935566ms message: 'load-balancer-api-external: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:48:41Z" - latency: 3.971451ms message: 'load-balancer-api-external: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 8.236746ms message: 'load-balancer-api-external: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:47:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "62386" uid: 9e099fa2-8117-45de-bbd8-78a14b8ae9e5 spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T12:21:41Z" message: 'load-balancer-api-internal: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.526634ms message: 'load-balancer-api-internal: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:51:41Z" - latency: 7.059631ms message: 'load-balancer-api-internal: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:51:41Z" - latency: 4.127175ms message: 'load-balancer-api-internal: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 7.737349ms message: 'load-balancer-api-internal: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:50:41Z" - latency: 5.808466ms message: 'load-balancer-api-internal: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 6.874319ms message: 'load-balancer-api-internal: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:49:41Z" - latency: 5.198245ms message: 'load-balancer-api-internal: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 9.892533ms message: 'load-balancer-api-internal: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:48:41Z" - latency: 4.538115ms message: 'load-balancer-api-internal: tcp connection to a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 8.298488ms message: 'load-balancer-api-internal: resolved host name a67d490a33aa046a591658b871042c62-b6f9a98096c7d657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T12:47:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-network-check-target-ip-10-0-128-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "61536" uid: 9b716bc4-9115-4d94-9b7c-e0f10af8950f spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T12:22:41Z" message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.148056ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 2.263053ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 2.082919ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 2.607283ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 2.475215ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:46:41Z" - latency: 3.177136ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:45:41Z" - latency: 2.403971ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:44:41Z" - latency: 2.178704ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:43:41Z" - latency: 2.599028ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:42:41Z" - latency: 2.460261ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:41:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-network-check-target-ip-10-0-131-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "61535" uid: 543449e8-1f25-4a9a-b426-542b4202fa8e spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T12:22:41Z" message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.437614ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 2.086027ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 2.528262ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 2.5558ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 2.24175ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:46:41Z" - latency: 2.692548ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:45:41Z" - latency: 2.320495ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:44:41Z" - latency: 2.595364ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:43:41Z" - latency: 2.785423ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:42:41Z" - latency: 2.622341ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:41:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-network-check-target-ip-10-0-136-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "61534" uid: 6cbe075e-92e2-4adc-96af-45f5b67c82b5 spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T12:22:41Z" message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.21927ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 1.476033ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 922.027µs message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 1.021726ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 882.792µs message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:46:41Z" - latency: 916.502µs message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:45:41Z" - latency: 964.668µs message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:44:41Z" - latency: 1.737394ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:43:41Z" - latency: 1.221851ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:42:41Z" - latency: 1.083713ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:41:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-24.ec2.internal uid: ff951e65-9dac-4563-bbb1-864de1898d92 resourceVersion: "62385" uid: 5c24e42d-7c0b-4ea9-9fb6-129a212bb2dc spec: sourcePod: network-check-source-685456655f-rxp86 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T12:21:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.948µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:51:41Z" - latency: 1.727087ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T12:51:41Z" - latency: 1.075842ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:50:41Z" - latency: 1.843066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T12:50:41Z" - latency: 1.153121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:49:41Z" - latency: 2.00936ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T12:49:41Z" - latency: 919.36µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:48:41Z" - latency: 1.823636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T12:48:41Z" - latency: 955.105µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T12:47:41Z" - latency: 1.791198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T12:47:41Z" kind: List metadata: resourceVersion: ""