apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "43501" uid: dd76d5ae-eb86-4d95-b991-74af5f399410 spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T20:35:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.849µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 1.055848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 1.024089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 1.043667ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:53:35Z" - latency: 977.994µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:52:35Z" - latency: 983.087µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:51:35Z" - latency: 1.012809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:50:35Z" - latency: 766.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:49:35Z" - latency: 778.752µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:48:35Z" - latency: 750.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "45639" uid: d98423b6-7fce-449f-89e5-1742c5591053 spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T20:34:35Z" message: 'load-balancer-api-external: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.886291ms message: 'load-balancer-api-external: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:58:35Z" - latency: 10.363034ms message: 'load-balancer-api-external: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:58:35Z" - latency: 5.366595ms message: 'load-balancer-api-external: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:57:35Z" - latency: 6.973456ms message: 'load-balancer-api-external: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:57:35Z" - latency: 3.603068ms message: 'load-balancer-api-external: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 8.530578ms message: 'load-balancer-api-external: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:56:35Z" - latency: 3.933309ms message: 'load-balancer-api-external: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 7.82241ms message: 'load-balancer-api-external: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:55:35Z" - latency: 3.246596ms message: 'load-balancer-api-external: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 7.137933ms message: 'load-balancer-api-external: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:54:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "45640" uid: 6f56228d-991e-4de5-a7f4-f393181c7ba2 spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T20:34:35Z" message: 'load-balancer-api-internal: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.895411ms message: 'load-balancer-api-internal: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:58:35Z" - latency: 10.242026ms message: 'load-balancer-api-internal: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:58:35Z" - latency: 3.477641ms message: 'load-balancer-api-internal: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:57:35Z" - latency: 6.903197ms message: 'load-balancer-api-internal: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:57:35Z" - latency: 4.184513ms message: 'load-balancer-api-internal: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 8.569398ms message: 'load-balancer-api-internal: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:56:35Z" - latency: 4.265205ms message: 'load-balancer-api-internal: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 7.786471ms message: 'load-balancer-api-internal: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:55:35Z" - latency: 3.8348ms message: 'load-balancer-api-internal: tcp connection to abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 7.102238ms message: 'load-balancer-api-internal: resolved host name abbff5aa8604847ecac0be130afa0bc6-7d33c50c80db79c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:54:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-network-check-target-ip-10-0-134-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "43500" uid: 094fa68a-445a-4d6f-b073-bdbc897ba670 spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T20:35:35Z" message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.260316ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 2.017654ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 1.950361ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 2.285459ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:53:35Z" - latency: 2.15595ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:52:35Z" - latency: 2.182201ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:51:35Z" - latency: 2.278503ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:50:35Z" - latency: 1.804408ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:49:35Z" - latency: 1.782972ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:48:35Z" - latency: 2.008574ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-network-check-target-ip-10-0-137-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "43498" uid: 3b155353-3f23-4fd1-8cd3-9c652ba006de spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T20:35:35Z" message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 814.47µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 805.252µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 858.969µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 863.558µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:53:35Z" - latency: 752.579µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:52:35Z" - latency: 1.185516ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:51:35Z" - latency: 761.957µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:50:35Z" - latency: 1.329897ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:49:35Z" - latency: 859.08µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:48:35Z" - latency: 823.026µs message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-network-check-target-ip-10-0-137-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "43499" uid: 31a757e9-def7-48d1-a9a3-f186411eeedb spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T20:35:35Z" message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.735012ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 1.849036ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 1.79249ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 1.93683ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:53:35Z" - latency: 2.022998ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:52:35Z" - latency: 1.943377ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:51:35Z" - latency: 1.878561ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:50:35Z" - latency: 1.84784ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:49:35Z" - latency: 1.683975ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:48:35Z" - latency: 1.730806ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-153-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-153.ec2.internal uid: d4ac24ff-6b8e-4efe-986b-2327672bde61 resourceVersion: "45638" uid: 4876b16a-3a18-466c-9272-3f082327eee0 spec: sourcePod: network-check-source-7f44b6dd87-kvxnd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T20:34:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.129386ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:58:35Z" - latency: 1.555032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:58:35Z" - latency: 725.009µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:57:35Z" - latency: 1.736794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:57:35Z" - latency: 968.805µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:56:35Z" - latency: 1.66237ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:56:35Z" - latency: 892.939µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:55:35Z" - latency: 1.603829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:55:35Z" - latency: 962.015µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:54:35Z" - latency: 1.87048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:54:35Z" kind: List metadata: resourceVersion: ""