apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "44765" uid: a1a1959b-ae8d-4741-a990-b3acf0820354 spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T19:33:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 677.854µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 832.264µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 688.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 817.458µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:51:02Z" - latency: 828.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:50:02Z" - latency: 1.346727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:49:02Z" - latency: 724.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:48:02Z" - latency: 787.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:47:02Z" - latency: 749.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:46:02Z" - latency: 881.944µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:45:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "46678" uid: df66852c-1dba-4478-a120-ccd2a143ecc7 spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T19:32:02Z" message: 'load-balancer-api-external: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.704121ms message: 'load-balancer-api-external: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:56:02Z" - latency: 11.409946ms message: 'load-balancer-api-external: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:56:02Z" - latency: 3.700123ms message: 'load-balancer-api-external: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:55:02Z" - latency: 6.597795ms message: 'load-balancer-api-external: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:55:02Z" - latency: 4.269069ms message: 'load-balancer-api-external: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 8.164706ms message: 'load-balancer-api-external: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:54:02Z" - latency: 3.862816ms message: 'load-balancer-api-external: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 10.423794ms message: 'load-balancer-api-external: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:53:02Z" - latency: 4.668364ms message: 'load-balancer-api-external: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 8.709119ms message: 'load-balancer-api-external: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:52:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "46679" uid: 3b7bf7d6-818e-4c28-9383-e6c3e176c790 spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T19:32:02Z" message: 'load-balancer-api-internal: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.900314ms message: 'load-balancer-api-internal: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:56:02Z" - latency: 11.345261ms message: 'load-balancer-api-internal: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:56:02Z" - latency: 3.748694ms message: 'load-balancer-api-internal: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:55:02Z" - latency: 6.581855ms message: 'load-balancer-api-internal: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:55:02Z" - latency: 3.810323ms message: 'load-balancer-api-internal: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 8.126229ms message: 'load-balancer-api-internal: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:54:02Z" - latency: 3.852673ms message: 'load-balancer-api-internal: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 10.392751ms message: 'load-balancer-api-internal: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:53:02Z" - latency: 3.300353ms message: 'load-balancer-api-internal: tcp connection to a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 8.680724ms message: 'load-balancer-api-internal: resolved host name a7d4fd50a72d34841888c9dcb61ea657-7b1d2d13ddf70291.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:52:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-128-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "44764" uid: c5ceaa80-1d16-4e92-90df-93327f6cf4e5 spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T19:33:02Z" message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.15111ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 1.635784ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 978.619µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 1.279144ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:51:02Z" - latency: 1.411683ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:50:02Z" - latency: 1.008162ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:49:02Z" - latency: 765.851µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:48:02Z" - latency: 1.207857ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:47:02Z" - latency: 879.998µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:46:02Z" - latency: 1.191116ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:45:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-130-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "44763" uid: 34fbc145-9909-4963-b302-73e4989c5efb spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T19:33:02Z" message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.940242ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 2.178168ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 1.953382ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 2.145418ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:51:02Z" - latency: 2.173592ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:50:02Z" - latency: 2.075299ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:49:02Z" - latency: 2.167286ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:48:02Z" - latency: 2.114107ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:47:02Z" - latency: 2.111338ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:46:02Z" - latency: 2.114697ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:45:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-130-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "44762" uid: e405241f-339c-4c08-a9cb-d84e97a1b487 spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T19:33:02Z" message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.046136ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 2.297998ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 1.982325ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 2.035806ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:51:02Z" - latency: 2.162929ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:50:02Z" - latency: 2.049607ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:49:02Z" - latency: 2.192205ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:48:02Z" - latency: 1.912215ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:47:02Z" - latency: 2.234261ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:46:02Z" - latency: 2.515315ms message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:45:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:26:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 233caef2-43ab-40b1-88d3-e328daadfea6 resourceVersion: "46677" uid: 742698a2-d7fc-4d28-9414-b110b8c5f81f spec: sourcePod: network-check-source-8894fc9bd-9hfwk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T19:32:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.269878ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:56:02Z" - latency: 2.564711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:56:02Z" - latency: 943.799µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:55:02Z" - latency: 1.659047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:55:02Z" - latency: 1.000495ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:54:02Z" - latency: 1.923393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:54:02Z" - latency: 1.27758ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:53:02Z" - latency: 1.610314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:53:02Z" - latency: 907.82µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:52:02Z" - latency: 1.768228ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:52:02Z" kind: List metadata: resourceVersion: ""