apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201995" uid: fa585414-ee9b-4d8a-bfcf-841953ecc8bb spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T00:14:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:38:17Z" - latency: 1.267286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 2.450323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 937.88µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 1.121281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 1.587756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 1.042016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:32:17Z" - latency: 1.005092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:31:17Z" - latency: 811.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:30:17Z" - latency: 964.03µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:29:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201284" uid: e38e2b25-f1a4-4536-8fc9-4893e24a4bfa spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T00:13:17Z" message: 'load-balancer-api-external: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.981622ms message: 'load-balancer-api-external: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 8.13205ms message: 'load-balancer-api-external: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:37:17Z" - latency: 16.611085ms message: 'load-balancer-api-external: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 9.03702ms message: 'load-balancer-api-external: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:36:17Z" - latency: 13.929863ms message: 'load-balancer-api-external: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 7.368577ms message: 'load-balancer-api-external: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:35:17Z" - latency: 13.60703ms message: 'load-balancer-api-external: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 7.618792ms message: 'load-balancer-api-external: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:34:17Z" - latency: 15.215932ms message: 'load-balancer-api-external: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 7.054912ms message: 'load-balancer-api-external: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:33:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201285" uid: a65abfea-570c-46b1-be49-2d624c3767b3 spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T00:13:17Z" message: 'load-balancer-api-internal: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.033814ms message: 'load-balancer-api-internal: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 8.091084ms message: 'load-balancer-api-internal: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:37:17Z" - latency: 15.042979ms message: 'load-balancer-api-internal: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 9.004584ms message: 'load-balancer-api-internal: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:36:17Z" - latency: 15.305971ms message: 'load-balancer-api-internal: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 7.305677ms message: 'load-balancer-api-internal: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:35:17Z" - latency: 13.605552ms message: 'load-balancer-api-internal: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 7.642878ms message: 'load-balancer-api-internal: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:34:17Z" - latency: 15.246252ms message: 'load-balancer-api-internal: tcp connection to a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 6.897416ms message: 'load-balancer-api-internal: resolved host name a5802885a2f1f479aa7a2de97f912243-87df652daba047b7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:33:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-network-check-target-ip-10-0-133-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201993" uid: 754a2cfd-dae1-4dac-843f-1748c0b7372f spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:14:17Z" message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 894.355µs message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:38:17Z" - latency: 1.105075ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 939.546µs message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 1.221211ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 1.016099ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 926.662µs message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 1.175512ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:32:17Z" - latency: 1.287942ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:31:17Z" - latency: 816.528µs message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:30:17Z" - latency: 1.359193ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:29:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-network-check-target-ip-10-0-133-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201994" uid: 98695071-65cc-40a7-b877-431a50de39bc spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:14:17Z" message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.711524ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:38:17Z" - latency: 1.990145ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 2.21958ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 2.244612ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 2.188733ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 2.06441ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 1.98341ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:32:17Z" - latency: 1.995284ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:31:17Z" - latency: 2.190493ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:30:17Z" - latency: 2.098738ms message: 'network-check-target-ip-10-0-133-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:29:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-network-check-target-ip-10-0-136-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201992" uid: 3f7be48e-643a-430a-83c7-b9c8e3e0e03f spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:14:17Z" message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.06208ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:38:17Z" - latency: 2.477504ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 2.806182ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 2.568372ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 2.149915ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 2.188686ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 2.341478ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:32:17Z" - latency: 1.925725ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:31:17Z" - latency: 2.323559ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:30:17Z" - latency: 2.180158ms message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:29:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:07:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-161.ec2.internal uid: 331d2794-5827-4fe6-93e4-4b478e6c156d resourceVersion: "201283" uid: a438bc7c-22a8-4e34-b9a7-13faa43fe9a4 spec: sourcePod: network-check-source-6f78d59f99-8mjkf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T00:13:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.338883ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:37:17Z" - latency: 2.043629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:37:17Z" - latency: 985.192µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:36:17Z" - latency: 3.71549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:36:17Z" - latency: 960.268µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:35:17Z" - latency: 1.949758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:35:17Z" - latency: 941.189µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:34:17Z" - latency: 2.516837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:34:17Z" - latency: 832.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:33:17Z" - latency: 1.885244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:33:17Z" kind: List metadata: resourceVersion: ""