apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "52081" uid: c0f8a372-4d35-4cd7-9d72-83eb2253a77f spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T20:54:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.032µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 1.16613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 849.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 1.843176ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 1.027371ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:18:58Z" - latency: 1.109082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:17:58Z" - latency: 1.123659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:16:58Z" - latency: 761.86µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:15:58Z" - latency: 1.565233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:14:58Z" - latency: 895.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:13:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "53211" uid: 2c6a7ca3-cc27-4d55-ab70-5112f7f3b3b0 spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T20:53:58Z" message: 'load-balancer-api-external: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.687051ms message: 'load-balancer-api-external: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:23:58Z" - latency: 8.190648ms message: 'load-balancer-api-external: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:23:58Z" - latency: 4.214681ms message: 'load-balancer-api-external: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 8.4891ms message: 'load-balancer-api-external: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:22:58Z" - latency: 3.783597ms message: 'load-balancer-api-external: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 8.530557ms message: 'load-balancer-api-external: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:21:58Z" - latency: 3.170656ms message: 'load-balancer-api-external: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 8.245864ms message: 'load-balancer-api-external: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:20:58Z" - latency: 4.823966ms message: 'load-balancer-api-external: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 8.461896ms message: 'load-balancer-api-external: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:19:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "53210" uid: fe099664-20a4-4a66-934a-bc19340021ac spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T20:53:58Z" message: 'load-balancer-api-internal: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.657345ms message: 'load-balancer-api-internal: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:23:58Z" - latency: 8.130998ms message: 'load-balancer-api-internal: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:23:58Z" - latency: 4.199374ms message: 'load-balancer-api-internal: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 8.412184ms message: 'load-balancer-api-internal: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:22:58Z" - latency: 4.330409ms message: 'load-balancer-api-internal: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 8.454905ms message: 'load-balancer-api-internal: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:21:58Z" - latency: 5.064716ms message: 'load-balancer-api-internal: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 8.191389ms message: 'load-balancer-api-internal: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:20:58Z" - latency: 4.54809ms message: 'load-balancer-api-internal: tcp connection to a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 8.360672ms message: 'load-balancer-api-internal: resolved host name a67f55aa32d4140f8b8d314b6f2d82e6-40c0e80d3a146cbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T21:19:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-network-check-target-ip-10-0-139-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "52078" uid: 5ce02bd3-98c4-4bb0-ac8f-1be07d0e23b7 spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T20:54:58Z" message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.217227ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 1.311188ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 1.144038ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 1.176317ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 787.345µs message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:18:58Z" - latency: 1.495806ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:17:58Z" - latency: 895.135µs message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:16:58Z" - latency: 1.014915ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:15:58Z" - latency: 832.142µs message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:14:58Z" - latency: 1.016994ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:13:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-network-check-target-ip-10-0-140-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "52080" uid: 38ab7ee3-a1b5-4fe7-9e4f-0e88fbe14083 spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T20:54:58Z" message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.349817ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 2.35208ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 2.320013ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 2.181826ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 2.231072ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:18:58Z" - latency: 2.194276ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:17:58Z" - latency: 2.299849ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:16:58Z" - latency: 2.269685ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:15:58Z" - latency: 2.294535ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:14:58Z" - latency: 2.369825ms message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:13:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-network-check-target-ip-10-0-142-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "52079" uid: 87290701-03b1-4bc2-951f-023c6228af36 spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T20:54:58Z" message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.953823ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 1.960464ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 1.838698ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 1.779682ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 1.975033ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:18:58Z" - latency: 2.183094ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:17:58Z" - latency: 2.031267ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:16:58Z" - latency: 1.52017ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:15:58Z" - latency: 2.058245ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:14:58Z" - latency: 2.098404ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:13:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:47:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-104.ec2.internal uid: e86a8a04-acf6-4553-aafa-8999ead7f831 resourceVersion: "53209" uid: 6361623d-de59-4b2a-9c51-0b3cb7f74cee spec: sourcePod: network-check-source-dbd9cf844-w7x69 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T20:53:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005513ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:23:58Z" - latency: 2.43857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T21:23:58Z" - latency: 1.093113ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:22:58Z" - latency: 1.679391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T21:22:58Z" - latency: 882.771µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:21:58Z" - latency: 1.944691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T21:21:58Z" - latency: 1.150318ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:20:58Z" - latency: 1.604215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T21:20:58Z" - latency: 768.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T21:19:58Z" - latency: 1.860513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T21:19:58Z" kind: List metadata: resourceVersion: ""