apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231453" uid: affa0d1d-bdce-4761-8ea5-5220222f6f12 spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:09:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.208127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 1.346936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 1.504472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 1.31525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 1.337769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 1.051907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:54Z" - latency: 1.379979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:54Z" - latency: 888.221µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:54Z" - latency: 919.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:54Z" - latency: 1.279504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231454" uid: 2aa68d47-8cce-4280-a78c-1d4e686749f2 spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:08:54Z" message: 'load-balancer-api-external: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.033836ms message: 'load-balancer-api-external: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 6.959642ms message: 'load-balancer-api-external: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:26:54Z" - latency: 4.865839ms message: 'load-balancer-api-external: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 7.344218ms message: 'load-balancer-api-external: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:25:54Z" - latency: 6.22191ms message: 'load-balancer-api-external: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 53.718426ms message: 'load-balancer-api-external: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:24:54Z" - latency: 6.150385ms message: 'load-balancer-api-external: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 6.761291ms message: 'load-balancer-api-external: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:23:54Z" - latency: 6.364768ms message: 'load-balancer-api-external: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 7.80391ms message: 'load-balancer-api-external: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:22:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231455" uid: ab9d3fa6-fe32-42ec-a6c8-d43a73be137a spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:08:54Z" message: 'load-balancer-api-internal: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.027375ms message: 'load-balancer-api-internal: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 6.984154ms message: 'load-balancer-api-internal: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:26:54Z" - latency: 4.856757ms message: 'load-balancer-api-internal: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 7.378757ms message: 'load-balancer-api-internal: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:25:54Z" - latency: 6.21084ms message: 'load-balancer-api-internal: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 53.678548ms message: 'load-balancer-api-internal: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:24:54Z" - latency: 6.147221ms message: 'load-balancer-api-internal: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 6.808223ms message: 'load-balancer-api-internal: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:23:54Z" - latency: 5.404655ms message: 'load-balancer-api-internal: tcp connection to a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 7.870889ms message: 'load-balancer-api-internal: resolved host name a43dec4d9dc644f8f9c4d13536caa3f0-796962e4feb735ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:22:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-network-check-target-ip-10-0-142-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231449" uid: bf728d3e-8c1e-4b00-9f9c-e6b1581cbcff spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:09:54Z" message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.030263ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 2.224946ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 1.823125ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 2.094349ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 1.801751ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 2.013363ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:54Z" - latency: 2.945769ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:54Z" - latency: 1.725046ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:54Z" - latency: 1.735273ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:54Z" - latency: 1.802714ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-network-check-target-ip-10-0-143-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231451" uid: 3c37c914-4712-4338-b26c-9749a1f837dd spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:09:54Z" message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.395373ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 2.201333ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 3.214371ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 2.354755ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 2.017629ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 2.041408ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:54Z" - latency: 2.48438ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:54Z" - latency: 1.844932ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:54Z" - latency: 2.045442ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:54Z" - latency: 2.103429ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-network-check-target-ip-10-0-143-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231450" uid: a29bcabe-b3f5-4ec9-a3b4-72ccdd1faa17 spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:09:54Z" message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.668079ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 1.801713ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 864.8µs message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 1.00821ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 1.372076ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 1.318815ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:54Z" - latency: 1.097764ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:54Z" - latency: 1.736076ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:54Z" - latency: 1.250382ms message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:54Z" - latency: 963.766µs message: 'network-check-target-ip-10-0-143-81: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-81-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-81.us-east-2.compute.internal uid: 92abd2e8-2875-4ca9-b10e-a6aa92ed7264 resourceVersion: "231452" uid: a0e92116-8018-43ec-8bd6-2bd4e999a4e9 spec: sourcePod: network-check-source-6f78d59f99-6tmll targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:08:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.118423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:54Z" - latency: 1.79575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:26:54Z" - latency: 959.418µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:54Z" - latency: 2.194119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:25:54Z" - latency: 877.442µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:54Z" - latency: 1.932154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:24:54Z" - latency: 1.12939ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:54Z" - latency: 1.792001ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:23:54Z" - latency: 929.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:54Z" - latency: 2.318512ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:22:54Z" kind: List metadata: resourceVersion: ""