apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "102502" uid: 344ffc65-9ad2-4abb-81a0-4d814ece2696 spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:42:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 977.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:19Z" - latency: 966.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:12:19Z" - latency: 1.00378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 1.008428ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 1.177546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 1.335724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 1.464519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 904.904µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:06:19Z" - latency: 1.408326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:05:19Z" - latency: 1.49935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:04:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "100902" uid: b7363720-687a-40dd-8d5d-4f628f68d7e9 spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:41:19Z" message: 'load-balancer-api-external: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.427166ms message: 'load-balancer-api-external: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 9.37968ms message: 'load-balancer-api-external: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:11:19Z" - latency: 7.134673ms message: 'load-balancer-api-external: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 12.482675ms message: 'load-balancer-api-external: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:10:19Z" - latency: 4.970748ms message: 'load-balancer-api-external: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 10.149478ms message: 'load-balancer-api-external: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:09:19Z" - latency: 4.289288ms message: 'load-balancer-api-external: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 7.850243ms message: 'load-balancer-api-external: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:08:19Z" - latency: 4.397113ms message: 'load-balancer-api-external: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 8.914316ms message: 'load-balancer-api-external: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:07:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "100901" uid: 631ee24c-5c8b-41be-8218-942b5e8bc78c spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:41:19Z" message: 'load-balancer-api-internal: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 13.890445ms message: 'load-balancer-api-internal: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 9.486482ms message: 'load-balancer-api-internal: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:11:19Z" - latency: 4.460787ms message: 'load-balancer-api-internal: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 12.404167ms message: 'load-balancer-api-internal: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:10:19Z" - latency: 4.88463ms message: 'load-balancer-api-internal: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 10.221935ms message: 'load-balancer-api-internal: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:09:19Z" - latency: 6.019552ms message: 'load-balancer-api-internal: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 7.94273ms message: 'load-balancer-api-internal: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:08:19Z" - latency: 4.336227ms message: 'load-balancer-api-internal: tcp connection to a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 8.943764ms message: 'load-balancer-api-internal: resolved host name a0efbcaf2b82142f4a016b251d320527-bc087ef89d600dae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:07:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-network-check-target-ip-10-0-131-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "102499" uid: 03479b1e-59c6-4103-9cc9-70f62c00891e spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:42:19Z" message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.845µs message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:19Z" - latency: 1.181801ms message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:12:19Z" - latency: 1.005362ms message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 1.367269ms message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 1.128018ms message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 1.05276ms message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 894.961µs message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 1.020836ms message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:06:19Z" - latency: 822.233µs message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:05:19Z" - latency: 912.77µs message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:04:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-network-check-target-ip-10-0-131-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "102501" uid: 5fea6096-a3ce-4f8d-a3d8-c2275ea001a3 spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:42:19Z" message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.239696ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:19Z" - latency: 1.986192ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:12:19Z" - latency: 2.279872ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 2.583581ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 2.501993ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 2.516416ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 2.079389ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 2.139853ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:06:19Z" - latency: 2.226343ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:05:19Z" - latency: 2.4208ms message: 'network-check-target-ip-10-0-131-74: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:04:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-network-check-target-ip-10-0-135-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "102500" uid: af4edd97-5c6a-4146-b0b0-936b2295d673 spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:42:19Z" message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.171924ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:19Z" - latency: 2.325176ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:12:19Z" - latency: 2.359073ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 2.382736ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 2.529236ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 2.507153ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 2.302418ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 3.041455ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:06:19Z" - latency: 2.74979ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:05:19Z" - latency: 2.457359ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:04:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:35:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-114-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-114.ec2.internal uid: e6698237-8691-43c0-9651-6d63ad2ae05c resourceVersion: "100900" uid: 0f60e87b-edb6-4faf-b299-b3194d6c0cc8 spec: sourcePod: network-check-source-7d88cb55d8-8wzwg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:41:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.446µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:11:19Z" - latency: 1.649371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:11:19Z" - latency: 767.908µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:10:19Z" - latency: 2.060557ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:10:19Z" - latency: 1.200394ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:09:19Z" - latency: 1.694604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:09:19Z" - latency: 899.981µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:08:19Z" - latency: 1.826318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:08:19Z" - latency: 1.165902ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:07:19Z" - latency: 2.012666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:07:19Z" kind: List metadata: resourceVersion: ""