apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64361" uid: df06427f-83f0-491d-8f08-c28ecccc4e5c spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T19:10:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 925.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 787.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 1.344897ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 1.41869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 993.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:40:47Z" - latency: 1.257302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:39:47Z" - latency: 909.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:38:47Z" - latency: 1.127266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:37:47Z" - latency: 855.209µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:36:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64365" uid: 2d4aba9e-d766-4922-bc25-a659a29a7ca6 spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T19:09:47Z" message: 'load-balancer-api-external: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.162703ms message: 'load-balancer-api-external: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 9.097918ms message: 'load-balancer-api-external: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:45:47Z" - latency: 3.80508ms message: 'load-balancer-api-external: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 8.453438ms message: 'load-balancer-api-external: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:44:47Z" - latency: 3.998765ms message: 'load-balancer-api-external: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 8.579448ms message: 'load-balancer-api-external: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:43:47Z" - latency: 4.262142ms message: 'load-balancer-api-external: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 8.323383ms message: 'load-balancer-api-external: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:42:47Z" - latency: 4.407749ms message: 'load-balancer-api-external: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 9.455137ms message: 'load-balancer-api-external: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:41:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64364" uid: 8f9399b0-2026-45e9-8a5a-f6409ca51e18 spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T19:09:47Z" message: 'load-balancer-api-internal: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.1522ms message: 'load-balancer-api-internal: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 9.169682ms message: 'load-balancer-api-internal: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:45:47Z" - latency: 3.830437ms message: 'load-balancer-api-internal: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 8.391417ms message: 'load-balancer-api-internal: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:44:47Z" - latency: 5.070245ms message: 'load-balancer-api-internal: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 8.526356ms message: 'load-balancer-api-internal: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:43:47Z" - latency: 5.877493ms message: 'load-balancer-api-internal: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 8.132587ms message: 'load-balancer-api-internal: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:42:47Z" - latency: 3.168316ms message: 'load-balancer-api-internal: tcp connection to a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 9.535669ms message: 'load-balancer-api-internal: resolved host name a043e90ecf6d84adb82bd893b3fa0cca-0ef8ae0f896450fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:41:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-network-check-target-ip-10-0-135-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64358" uid: 835a7504-c7d9-49d1-a15d-fc28e32ad0aa spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:10:47Z" message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.035037ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 2.111621ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 2.208614ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 2.949959ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 2.12051ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 2.133843ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:40:47Z" - latency: 2.165201ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:39:47Z" - latency: 2.431496ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:38:47Z" - latency: 2.179389ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:37:47Z" - latency: 2.187142ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:36:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-network-check-target-ip-10-0-139-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64359" uid: 59153660-db9e-44dc-af7b-715f22c83b20 spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:10:47Z" message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.094007ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 2.202263ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 1.793587ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 3.017454ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 1.962249ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 1.851793ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:40:47Z" - latency: 1.693654ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:39:47Z" - latency: 2.097366ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:38:47Z" - latency: 2.025149ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:37:47Z" - latency: 1.691318ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:36:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-network-check-target-ip-10-0-140-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64357" uid: f624070b-56e3-48f9-ab74-5df6b0d7a9bd spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:10:47Z" message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175409ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 909.287µs message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 1.189132ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 2.031274ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 781.504µs message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 1.387919ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:40:47Z" - latency: 784.918µs message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:39:47Z" - latency: 1.079445ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:38:47Z" - latency: 921.751µs message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:37:47Z" - latency: 896.949µs message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:36:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:03:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-250.ec2.internal uid: 3df8254f-b964-48c0-bca4-6c8d82f418a1 resourceVersion: "64360" uid: b86d101e-e66a-402b-a76c-00652ed4c05d spec: sourcePod: network-check-source-7bc5b6bf85-v8pdx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T19:09:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.826µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:45:47Z" - latency: 2.083918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:45:47Z" - latency: 863.625µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:44:47Z" - latency: 1.831081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:44:47Z" - latency: 739.233µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:43:47Z" - latency: 2.226822ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:43:47Z" - latency: 1.162328ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:42:47Z" - latency: 2.116396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:42:47Z" - latency: 1.082263ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:41:47Z" - latency: 1.549103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:41:47Z" kind: List metadata: resourceVersion: ""