apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "44970" uid: 80c5b0ca-67b6-4728-928c-8e18c52e6de5 spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T21:21:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014168ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:42:46Z" - latency: 1.068861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:41:46Z" - latency: 934.506µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:40:46Z" - latency: 1.093457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:39:46Z" - latency: 1.143979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 1.151279ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 1.95903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 989.529µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 798.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 1.109088ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:33:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "40427" uid: c3cdb992-f4e1-41ac-965c-5d2f0de3ac08 spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T21:20:46Z" message: 'load-balancer-api-external: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.088129ms message: 'load-balancer-api-external: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 6.66624ms message: 'load-balancer-api-external: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:38:46Z" - latency: 5.644804ms message: 'load-balancer-api-external: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 6.211607ms message: 'load-balancer-api-external: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:37:46Z" - latency: 4.338052ms message: 'load-balancer-api-external: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 8.252211ms message: 'load-balancer-api-external: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:36:46Z" - latency: 4.670612ms message: 'load-balancer-api-external: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 7.352594ms message: 'load-balancer-api-external: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:35:46Z" - latency: 3.890811ms message: 'load-balancer-api-external: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 6.594382ms message: 'load-balancer-api-external: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:34:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "40426" uid: df2ef337-249b-459f-884a-5296a4ea9c0c spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T21:20:46Z" message: 'load-balancer-api-internal: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.060732ms message: 'load-balancer-api-internal: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 6.752806ms message: 'load-balancer-api-internal: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:38:46Z" - latency: 5.652702ms message: 'load-balancer-api-internal: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 6.135111ms message: 'load-balancer-api-internal: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:37:46Z" - latency: 6.68994ms message: 'load-balancer-api-internal: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 8.203757ms message: 'load-balancer-api-internal: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:36:46Z" - latency: 5.21284ms message: 'load-balancer-api-internal: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 7.328704ms message: 'load-balancer-api-internal: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:35:46Z" - latency: 3.873252ms message: 'load-balancer-api-internal: tcp connection to ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 6.680896ms message: 'load-balancer-api-internal: resolved host name ad0647f4cfe5c42d2a0c2c1c3b33877e-551e733294b6e21a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T21:34:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-ip-10-0-134-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "44969" uid: 079e6369-61b7-43c5-be92-aead814f729a spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T21:21:46Z" message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.252683ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:42:46Z" - latency: 2.326766ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:41:46Z" - latency: 2.067322ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:40:46Z" - latency: 2.07282ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:39:46Z" - latency: 2.207614ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 2.063967ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 2.529765ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 2.065297ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 1.877561ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 2.203476ms message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:33:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-ip-10-0-136-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "44968" uid: 6411ed28-e8fe-4edd-84c5-2dedb394b241 spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T21:21:46Z" message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.869909ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:42:46Z" - latency: 1.987033ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:41:46Z" - latency: 1.793957ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:40:46Z" - latency: 2.048313ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:39:46Z" - latency: 1.895637ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 1.918338ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 2.226597ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 1.837764ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 1.516855ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 2.014491ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:33:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-ip-10-0-143-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "44967" uid: 02a0eaef-21a3-40c8-a330-08edefcb4614 spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T21:21:46Z" message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.709µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:42:46Z" - latency: 811.155µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:41:46Z" - latency: 1.526158ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:40:46Z" - latency: 1.04802ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:39:46Z" - latency: 870.094µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 815.775µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 2.057312ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 867.179µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 852.737µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 909.948µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:33:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T21:14:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.ec2.internal uid: 07a2d55f-1725-4234-a5ed-bea7b187a9a6 resourceVersion: "40424" uid: c13f6729-fa19-4026-b653-511bb5162dbe spec: sourcePod: network-check-source-8894fc9bd-jhrq6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T21:20:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.306µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:38:46Z" - latency: 1.638567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T21:38:46Z" - latency: 1.178054ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:37:46Z" - latency: 1.657624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T21:37:46Z" - latency: 1.345208ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:36:46Z" - latency: 1.818755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T21:36:46Z" - latency: 859.055µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:35:46Z" - latency: 1.86833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T21:35:46Z" - latency: 1.040504ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T21:34:46Z" - latency: 1.656943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T21:34:46Z" kind: List metadata: resourceVersion: ""