apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60637" uid: 430ec650-bbe4-42cb-ab4b-c8085ef78447 spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T01:09:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 968.395µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 998.947µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 1.210358ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 1.162067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 1.119867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:58Z" - latency: 1.129145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:38:58Z" - latency: 1.216008ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:37:58Z" - latency: 1.045551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:36:58Z" - latency: 1.280679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:35:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60638" uid: ce00fd3a-51a4-4e19-b004-bb9e2c75da00 spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T01:08:58Z" message: 'load-balancer-api-external: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.294958ms message: 'load-balancer-api-external: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 6.519631ms message: 'load-balancer-api-external: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:44:58Z" - latency: 5.819109ms message: 'load-balancer-api-external: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 9.146238ms message: 'load-balancer-api-external: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:43:58Z" - latency: 3.673545ms message: 'load-balancer-api-external: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 6.37229ms message: 'load-balancer-api-external: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:42:58Z" - latency: 6.990908ms message: 'load-balancer-api-external: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 6.595939ms message: 'load-balancer-api-external: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:41:58Z" - latency: 5.883301ms message: 'load-balancer-api-external: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 7.197419ms message: 'load-balancer-api-external: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:40:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60639" uid: 07f01b4a-b6d0-4a4f-8b01-0c0cfcbef6fc spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T01:08:58Z" message: 'load-balancer-api-internal: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.131354ms message: 'load-balancer-api-internal: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 6.45329ms message: 'load-balancer-api-internal: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:44:58Z" - latency: 10.887324ms message: 'load-balancer-api-internal: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 9.121813ms message: 'load-balancer-api-internal: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:43:58Z" - latency: 3.584036ms message: 'load-balancer-api-internal: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 6.321577ms message: 'load-balancer-api-internal: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:42:58Z" - latency: 5.0137ms message: 'load-balancer-api-internal: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 6.531796ms message: 'load-balancer-api-internal: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:41:58Z" - latency: 4.963238ms message: 'load-balancer-api-internal: tcp connection to a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 7.226065ms message: 'load-balancer-api-internal: resolved host name a2c2bdcc27b264218b8f93172afc4a28-80a00cbc50f10a8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:40:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-network-check-target-ip-10-0-131-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60635" uid: a2eb4a74-69fb-4697-a74d-d723f8499745 spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T01:09:58Z" message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.464348ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 2.013717ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 2.191579ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 2.248486ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 2.166468ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 2.450096ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:58Z" - latency: 2.386773ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:38:58Z" - latency: 2.273647ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:37:58Z" - latency: 2.734788ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:36:58Z" - latency: 2.476516ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:35:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-network-check-target-ip-10-0-138-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60634" uid: c4f67734-1c1b-4a49-8722-54260f195fa5 spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T01:09:58Z" message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.205734ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 2.396866ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 2.168274ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 2.425956ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 2.37841ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 2.355625ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:58Z" - latency: 2.47274ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:38:58Z" - latency: 2.120523ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:37:58Z" - latency: 2.459516ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:36:58Z" - latency: 2.125878ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:35:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-network-check-target-ip-10-0-143-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60633" uid: 9e949862-2b1b-4efd-8dae-cc5f3f9d18cb spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T01:09:58Z" message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.945µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 928.654µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 884.001µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 874.207µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 908.203µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 1.255407ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:58Z" - latency: 1.366237ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:38:58Z" - latency: 1.313771ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:37:58Z" - latency: 983.751µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:36:58Z" - latency: 892.423µs message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:35:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:02:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-159-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-159.ec2.internal uid: 5bd580c2-a898-412b-9e17-8f1f4c44349c resourceVersion: "60636" uid: 2f91c5f2-0487-4f79-b10e-e3fe256c7f5d spec: sourcePod: network-check-source-869dcfcdcd-8cpht targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T01:08:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:58Z" - latency: 1.917302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:44:58Z" - latency: 1.23932ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:58Z" - latency: 1.782227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:43:58Z" - latency: 923.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:58Z" - latency: 1.682021ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:42:58Z" - latency: 856.669µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:58Z" - latency: 1.712996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:41:58Z" - latency: 898.581µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:58Z" - latency: 1.67342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:40:58Z" kind: List metadata: resourceVersion: ""