apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "20909" uid: ed9c8996-3743-4667-9da1-a9e05a2d1328 spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.135441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 987.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 1.064297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 888.756µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:04:45Z" - latency: 1.04078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:03:45Z" - latency: 907.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:02:45Z" - latency: 1.020934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:01:45Z" - latency: 1.997575ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:00:45Z" - latency: 1.043478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:59:45Z" - latency: 898.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:58:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "21637" uid: 5a013f2c-f464-465e-90d0-b6abfb7992ce spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:45:45Z" message: 'load-balancer-api-external: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 23.431337ms message: 'load-balancer-api-external: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:45Z" - latency: 9.200396ms message: 'load-balancer-api-external: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:09:45Z" - latency: 17.04589ms message: 'load-balancer-api-external: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 8.815418ms message: 'load-balancer-api-external: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:08:45Z" - latency: 16.35803ms message: 'load-balancer-api-external: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 9.321223ms message: 'load-balancer-api-external: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:07:45Z" - latency: 15.008096ms message: 'load-balancer-api-external: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 8.925554ms message: 'load-balancer-api-external: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:06:45Z" - latency: 17.449945ms message: 'load-balancer-api-external: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 8.291369ms message: 'load-balancer-api-external: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:05:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "21638" uid: 699fc525-1458-4bad-8ac9-82c84eed071c spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:45:45Z" message: 'load-balancer-api-internal: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 35.779909ms message: 'load-balancer-api-internal: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:45Z" - latency: 9.162765ms message: 'load-balancer-api-internal: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:09:45Z" - latency: 17.031615ms message: 'load-balancer-api-internal: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 8.769547ms message: 'load-balancer-api-internal: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:08:45Z" - latency: 15.854506ms message: 'load-balancer-api-internal: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 9.254366ms message: 'load-balancer-api-internal: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:07:45Z" - latency: 14.545312ms message: 'load-balancer-api-internal: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 8.862717ms message: 'load-balancer-api-internal: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:06:45Z" - latency: 18.480293ms message: 'load-balancer-api-internal: tcp connection to af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 8.215273ms message: 'load-balancer-api-internal: resolved host name af59adb08a3e1476da8e9e4f920c64e2-24518fa6055d22eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:05:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-network-check-target-ip-10-0-132-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "20908" uid: 9cb2c02c-7849-42cd-afce-19578d3e1acf spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:45Z" message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.559818ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 918.41µs message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 1.554701ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 997.533µs message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:04:45Z" - latency: 1.017586ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:03:45Z" - latency: 911.41µs message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:02:45Z" - latency: 1.013032ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:01:45Z" - latency: 1.336648ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:00:45Z" - latency: 1.214139ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:59:45Z" - latency: 1.392767ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:58:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-network-check-target-ip-10-0-135-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "20907" uid: 1fd99d98-718d-4578-b494-fb23a9d8b1ea spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:45Z" message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.582782ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 2.34053ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 2.390736ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 2.172522ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:04:45Z" - latency: 2.429707ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:03:45Z" - latency: 2.302436ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:02:45Z" - latency: 2.27824ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:01:45Z" - latency: 2.608516ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:00:45Z" - latency: 2.216274ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:59:45Z" - latency: 2.555365ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:58:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-network-check-target-ip-10-0-143-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "20906" uid: c682b2ac-973a-4e69-9a18-708e5d426a14 spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:45Z" message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.520252ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 2.76446ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 2.809459ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 2.228695ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:04:45Z" - latency: 2.135101ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:03:45Z" - latency: 1.854324ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:02:45Z" - latency: 2.440572ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:01:45Z" - latency: 2.984837ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:00:45Z" - latency: 1.83125ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:59:45Z" - latency: 3.912938ms message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:58:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-168-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-168.ec2.internal uid: 00680ffa-2c93-405c-8b94-aec88e97f141 resourceVersion: "21636" uid: f620863d-2d1b-4922-8738-047059101e6e spec: sourcePod: network-check-source-6f78d59f99-49spc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:45:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178928ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:45Z" - latency: 1.888967ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:09:45Z" - latency: 907.114µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 1.888195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:08:45Z" - latency: 1.012508ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 2.5886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:07:45Z" - latency: 979.922µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - latency: 1.95474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:06:45Z" - latency: 1.192609ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:05:45Z" - latency: 1.733515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:05:45Z" kind: List metadata: resourceVersion: ""