apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "53526" uid: f1d55bd2-9c27-4cf7-b3da-0ef6fe2c42b8 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T17:51:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.034915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 1.258338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 1.202719ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 1.143221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:09:15Z" - latency: 1.41865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:08:15Z" - latency: 2.102873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:07:15Z" - latency: 915.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:06:15Z" - latency: 1.250119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:05:15Z" - latency: 1.17348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:04:15Z" - latency: 996.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "55098" uid: 0c979a08-f024-4a22-9d14-89bfbde6b301 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T17:50:15Z" message: 'load-balancer-api-external: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.379612ms message: 'load-balancer-api-external: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:14:15Z" - latency: 7.787415ms message: 'load-balancer-api-external: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:14:15Z" - latency: 4.641004ms message: 'load-balancer-api-external: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:13:15Z" - latency: 6.637782ms message: 'load-balancer-api-external: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:13:15Z" - latency: 4.702971ms message: 'load-balancer-api-external: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 7.648311ms message: 'load-balancer-api-external: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:12:15Z" - latency: 6.55875ms message: 'load-balancer-api-external: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 6.817812ms message: 'load-balancer-api-external: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:11:15Z" - latency: 6.935532ms message: 'load-balancer-api-external: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 7.426208ms message: 'load-balancer-api-external: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:10:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "55097" uid: c9a33570-5921-45c8-9aaf-c076ad24d442 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T17:50:15Z" message: 'load-balancer-api-internal: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.373595ms message: 'load-balancer-api-internal: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:14:15Z" - latency: 7.734875ms message: 'load-balancer-api-internal: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:14:15Z" - latency: 3.79408ms message: 'load-balancer-api-internal: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:13:15Z" - latency: 6.699013ms message: 'load-balancer-api-internal: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:13:15Z" - latency: 4.698732ms message: 'load-balancer-api-internal: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 7.596871ms message: 'load-balancer-api-internal: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:12:15Z" - latency: 6.57895ms message: 'load-balancer-api-internal: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 6.749857ms message: 'load-balancer-api-internal: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:11:15Z" - latency: 5.984194ms message: 'load-balancer-api-internal: tcp connection to a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 7.48143ms message: 'load-balancer-api-internal: resolved host name a72c5f422e251429e94c60ce27b628ce-e37bb71ea7e30355.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T18:10:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-network-check-target-ip-10-0-134-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "53525" uid: 8dd4f1a9-a009-4790-8de7-8e76e9dcd476 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T17:51:15Z" message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.524193ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 2.198751ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 2.203254ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 2.511887ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:09:15Z" - latency: 2.79481ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:08:15Z" - latency: 3.363114ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:07:15Z" - latency: 2.311266ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:06:15Z" - latency: 2.532778ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:05:15Z" - latency: 2.142382ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:04:15Z" - latency: 2.213627ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-network-check-target-ip-10-0-136-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "53524" uid: 39e88ac6-7428-4759-af16-4fff86e5fd23 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T17:51:15Z" message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.190889ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 1.429252ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 1.267811ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 910.419µs message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:09:15Z" - latency: 1.317856ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:08:15Z" - latency: 2.358326ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:07:15Z" - latency: 1.401863ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:06:15Z" - latency: 1.048648ms message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:05:15Z" - latency: 860.204µs message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:04:15Z" - latency: 996.442µs message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-network-check-target-ip-10-0-139-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "53523" uid: 876ef352-c5e3-4cd6-bfc1-ec7bdcf189b5 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T17:51:15Z" message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.124227ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 2.105095ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 2.267321ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 2.344541ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:09:15Z" - latency: 2.68912ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:08:15Z" - latency: 2.779483ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:07:15Z" - latency: 2.327821ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:06:15Z" - latency: 2.307134ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:05:15Z" - latency: 2.149292ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:04:15Z" - latency: 2.446187ms message: 'network-check-target-ip-10-0-139-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-161.ec2.internal uid: 3c8a4d6b-7017-41b0-82b5-7ca6c267aac5 resourceVersion: "55096" uid: 0a59ed56-4eb3-4e01-ad34-798b345e1916 spec: sourcePod: network-check-source-685456655f-vzfdh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T17:50:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 978.179µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:14:15Z" - latency: 2.00872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T18:14:15Z" - latency: 1.168384ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:13:15Z" - latency: 1.900589ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T18:13:15Z" - latency: 975.35µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:12:15Z" - latency: 2.060402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T18:12:15Z" - latency: 1.157566ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:11:15Z" - latency: 1.903593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T18:11:15Z" - latency: 1.125415ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T18:10:15Z" - latency: 2.213719ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T18:10:15Z" kind: List metadata: resourceVersion: ""