apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "241484" uid: a13ef3a9-4a5c-4bcb-bd23-f026cf413315 spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:39:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:13Z" - latency: 1.244418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:13Z" - latency: 1.100595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:13Z" - latency: 1.03288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:13Z" - latency: 1.006822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:03:13Z" - latency: 1.016237ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:02:13Z" - latency: 1.004129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:01:13Z" - latency: 1.01395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:13Z" - latency: 1.048235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:13Z" - latency: 1.375615ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "242025" uid: 94659863-f023-4676-b725-136050117ef5 spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:38:13Z" message: 'load-balancer-api-external: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.383691ms message: 'load-balancer-api-external: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:08:13Z" - latency: 7.072952ms message: 'load-balancer-api-external: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:08:13Z" - latency: 5.661774ms message: 'load-balancer-api-external: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:13Z" - latency: 6.413557ms message: 'load-balancer-api-external: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:07:13Z" - latency: 5.367055ms message: 'load-balancer-api-external: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:13Z" - latency: 7.345475ms message: 'load-balancer-api-external: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:06:13Z" - latency: 6.587429ms message: 'load-balancer-api-external: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:13Z" - latency: 6.545953ms message: 'load-balancer-api-external: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:05:13Z" - latency: 5.010968ms message: 'load-balancer-api-external: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:13Z" - latency: 10.093734ms message: 'load-balancer-api-external: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:04:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "242024" uid: 32ccd072-a083-4c05-bafa-e673a546bcda spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:38:13Z" message: 'load-balancer-api-internal: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.393463ms message: 'load-balancer-api-internal: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:08:13Z" - latency: 6.956449ms message: 'load-balancer-api-internal: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:08:13Z" - latency: 5.727349ms message: 'load-balancer-api-internal: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:13Z" - latency: 6.442248ms message: 'load-balancer-api-internal: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:07:13Z" - latency: 5.401074ms message: 'load-balancer-api-internal: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:13Z" - latency: 7.367634ms message: 'load-balancer-api-internal: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:06:13Z" - latency: 6.566626ms message: 'load-balancer-api-internal: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:13Z" - latency: 6.575469ms message: 'load-balancer-api-internal: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:05:13Z" - latency: 5.005134ms message: 'load-balancer-api-internal: tcp connection to acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:13Z" - latency: 10.121759ms message: 'load-balancer-api-internal: resolved host name acb016a5e504c4ca985d18876c4d6627-9b035d8de54f8ea2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:04:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-132-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "241892" uid: 96af4db2-cc83-434d-9649-e9670b20c790 spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:39:59Z" message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.250661ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:59Z" - latency: 2.193781ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:59Z" - latency: 1.873643ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:59Z" - latency: 2.326587ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:59Z" - latency: 3.594022ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:03:59Z" - latency: 5.540913ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:02:59Z" - latency: 3.549779ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:01:59Z" - latency: 2.052959ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:59Z" - latency: 2.108404ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:59Z" - latency: 2.249413ms message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-133-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "241482" uid: 5c2c526e-daca-4719-adda-40a2f9dd2cff spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:39:13Z" message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.963µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:13Z" - latency: 879.303µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:13Z" - latency: 1.390806ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:13Z" - latency: 985.502µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:13Z" - latency: 858.32µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:03:13Z" - latency: 958.395µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:02:13Z" - latency: 1.50619ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:01:13Z" - latency: 984.555µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:13Z" - latency: 765.701µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:13Z" - latency: 840.995µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-143-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "241483" uid: 20b1f89a-b669-4522-93b8-651117392820 spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:39:13Z" message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.405328ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:13Z" - latency: 2.290919ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:13Z" - latency: 2.632039ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:13Z" - latency: 2.430655ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:13Z" - latency: 2.240614ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:03:13Z" - latency: 2.494523ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:02:13Z" - latency: 2.484285ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:01:13Z" - latency: 2.585484ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:13Z" - latency: 2.425499ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:13Z" - latency: 2.507848ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.us-east-2.compute.internal uid: 999c100c-c7ff-45d3-b6e5-8cda64309aff resourceVersion: "242022" uid: 271b9b4b-054f-49c1-9cb3-60fcc430b104 spec: sourcePod: network-check-source-6f78d59f99-4ctkr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:38:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.934095ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:08:13Z" - latency: 1.729592ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:08:13Z" - latency: 965.532µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:07:13Z" - latency: 2.056373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:07:13Z" - latency: 894.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:06:13Z" - latency: 1.868801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:06:13Z" - latency: 1.185334ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:05:13Z" - latency: 2.116659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:05:13Z" - latency: 1.914198ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:04:13Z" - latency: 1.887428ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:04:13Z" kind: List metadata: resourceVersion: ""