apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "19250" uid: cf9c6ce2-09aa-42e0-9a1c-d4947e5916fd spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-07T14:09:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.146673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 1.017751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 884.29µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:21:37Z" - latency: 988.285µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:20:37Z" - latency: 861.269µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:19:37Z" - latency: 895.965µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:18:37Z" - latency: 1.101803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:17:37Z" - latency: 783.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:16:37Z" - latency: 918.108µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:15:37Z" - latency: 986.194µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "20481" uid: 78f31fb2-85b8-41bd-8076-b7f993fef562 spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T14:08:37Z" message: 'load-balancer-api-external: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.348815ms message: 'load-balancer-api-external: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:26:37Z" - latency: 7.469993ms message: 'load-balancer-api-external: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:26:37Z" - latency: 5.584141ms message: 'load-balancer-api-external: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:25:37Z" - latency: 8.522702ms message: 'load-balancer-api-external: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:25:37Z" - latency: 5.646238ms message: 'load-balancer-api-external: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:24:37Z" - latency: 10.219364ms message: 'load-balancer-api-external: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:24:37Z" - latency: 7.778866ms message: 'load-balancer-api-external: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 7.946375ms message: 'load-balancer-api-external: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:23:37Z" - latency: 5.377656ms message: 'load-balancer-api-external: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 10.151316ms message: 'load-balancer-api-external: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:22:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "20480" uid: fbe0cc4b-dcc8-4b84-9055-c5ce1ce0c1e3 spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T14:08:37Z" message: 'load-balancer-api-internal: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.329927ms message: 'load-balancer-api-internal: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:26:37Z" - latency: 7.539366ms message: 'load-balancer-api-internal: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:26:37Z" - latency: 5.377346ms message: 'load-balancer-api-internal: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:25:37Z" - latency: 8.468182ms message: 'load-balancer-api-internal: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:25:37Z" - latency: 5.660956ms message: 'load-balancer-api-internal: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:24:37Z" - latency: 10.532784ms message: 'load-balancer-api-internal: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:24:37Z" - latency: 4.884248ms message: 'load-balancer-api-internal: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 7.881768ms message: 'load-balancer-api-internal: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:23:37Z" - latency: 3.573087ms message: 'load-balancer-api-internal: tcp connection to af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 10.204154ms message: 'load-balancer-api-internal: resolved host name af09f79eaa0f44b78b9f48718a97f0b1-8f162abcb1e43438.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T14:22:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-network-check-target-ip-10-0-131-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "19248" uid: 23740abe-8595-4029-b7a2-22571d27a38c spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-07T14:09:37Z" message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.164917ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 2.001514ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 2.054164ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:21:37Z" - latency: 2.171221ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:20:37Z" - latency: 2.133077ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:19:37Z" - latency: 2.267263ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:18:37Z" - latency: 2.028607ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:17:37Z" - latency: 2.180833ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:16:37Z" - latency: 1.994669ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:15:37Z" - latency: 1.987431ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-network-check-target-ip-10-0-135-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "19249" uid: ff46ad7f-a5d7-4b26-bd53-f3d8a545a3a9 spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-07T14:09:37Z" message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.77589ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 1.85285ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 1.800305ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:21:37Z" - latency: 1.910548ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:20:37Z" - latency: 1.914242ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:19:37Z" - latency: 1.853423ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:18:37Z" - latency: 1.885414ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:17:37Z" - latency: 1.915376ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:16:37Z" - latency: 1.735819ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:15:37Z" - latency: 1.639726ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-network-check-target-ip-10-0-139-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "19247" uid: c6255f1d-f75d-4205-b391-ab74b69caba9 spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-07T14:09:37Z" message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.69µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 986.353µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 1.238613ms message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:21:37Z" - latency: 1.329794ms message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:20:37Z" - latency: 1.538626ms message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:19:37Z" - latency: 983.065µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:18:37Z" - latency: 792.975µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:17:37Z" - latency: 863.39µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:16:37Z" - latency: 957.812µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:15:37Z" - latency: 989.389µs message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T14:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-134.ec2.internal uid: 69230330-4f62-41c7-8a74-ad7c2c1931fd resourceVersion: "20479" uid: 28e70b41-8bc2-4104-9423-45db2d6c5977 spec: sourcePod: network-check-source-685456655f-b7xvd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-07T14:08:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.103893ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:26:37Z" - latency: 1.574185ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T14:26:37Z" - latency: 840.584µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:25:37Z" - latency: 1.857828ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T14:25:37Z" - latency: 980.439µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:24:37Z" - latency: 3.252742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T14:24:37Z" - latency: 1.132231ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:23:37Z" - latency: 1.785301ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T14:23:37Z" - latency: 852.961µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T14:22:37Z" - latency: 2.390255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T14:22:37Z" kind: List metadata: resourceVersion: ""