apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32141" uid: a4888949-f00d-44bb-bc04-efa73714e1a5 spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T16:45:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 800.542µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 920.081µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 1.221487ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 1.097228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 1.522961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 1.060183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:15:39Z" - latency: 1.305165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:14:39Z" - latency: 934.577µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:13:39Z" - latency: 681.097µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:12:39Z" - latency: 932.917µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:11:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32143" uid: 2bef159c-8980-4f66-8ba9-cf00b989294a spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:44:39Z" message: 'load-balancer-api-external: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.160994ms message: 'load-balancer-api-external: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 8.428951ms message: 'load-balancer-api-external: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:20:39Z" - latency: 4.172302ms message: 'load-balancer-api-external: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 10.326496ms message: 'load-balancer-api-external: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:19:39Z" - latency: 4.847944ms message: 'load-balancer-api-external: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 7.872182ms message: 'load-balancer-api-external: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:18:39Z" - latency: 5.710724ms message: 'load-balancer-api-external: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 8.189891ms message: 'load-balancer-api-external: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:17:39Z" - latency: 5.310548ms message: 'load-balancer-api-external: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 9.132022ms message: 'load-balancer-api-external: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:16:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32142" uid: 7b5dd949-8e10-4c57-bd4f-6752a4ca12b0 spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:44:39Z" message: 'load-balancer-api-internal: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.067563ms message: 'load-balancer-api-internal: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 8.474691ms message: 'load-balancer-api-internal: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:20:39Z" - latency: 3.946266ms message: 'load-balancer-api-internal: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 10.257259ms message: 'load-balancer-api-internal: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:19:39Z" - latency: 4.221658ms message: 'load-balancer-api-internal: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 7.935166ms message: 'load-balancer-api-internal: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:18:39Z" - latency: 5.705764ms message: 'load-balancer-api-internal: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 8.122314ms message: 'load-balancer-api-internal: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:17:39Z" - latency: 5.26124ms message: 'load-balancer-api-internal: tcp connection to a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 9.144817ms message: 'load-balancer-api-internal: resolved host name a63513de60bdb441389de069e0f208b3-33e3219231346705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:16:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-129-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32137" uid: f8e7c6f2-d2dd-40e5-9a4d-de9f1ee21794 spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:45:39Z" message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.000546ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 1.73726ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 911.09µs message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 657.397µs message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 1.545349ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 938.091µs message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:15:39Z" - latency: 1.146593ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:14:39Z" - latency: 1.389057ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:13:39Z" - latency: 1.195213ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:12:39Z" - latency: 1.246966ms message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:11:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-130-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32140" uid: 0ed17d0d-b218-459b-899d-df8116163b4d spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:45:39Z" message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.914545ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 1.98849ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 1.812309ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 1.785969ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 1.687128ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 1.854444ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:15:39Z" - latency: 1.915518ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:14:39Z" - latency: 1.752148ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:13:39Z" - latency: 1.57367ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:12:39Z" - latency: 2.047634ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:11:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-135-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32138" uid: ecb76369-386d-41be-a292-8cbfaed26e5e spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:45:39Z" message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.346865ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 2.124964ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 2.270281ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 2.038669ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 2.439228ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 2.234298ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:15:39Z" - latency: 2.282933ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:14:39Z" - latency: 2.216551ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:13:39Z" - latency: 1.931769ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:12:39Z" - latency: 2.560269ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:11:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:38:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-12.ec2.internal uid: fa629e46-fc5d-44d7-b184-47b3f22176ef resourceVersion: "32139" uid: 5a939b46-a653-4391-a52b-17aee4da390e spec: sourcePod: network-check-source-989f8b8dc-zh6r7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T16:44:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.78µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:20:39Z" - latency: 2.051284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:20:39Z" - latency: 805.872µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:19:39Z" - latency: 2.37662ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:19:39Z" - latency: 924.511µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:18:39Z" - latency: 1.687612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:18:39Z" - latency: 1.087332ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:17:39Z" - latency: 1.699014ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:17:39Z" - latency: 1.101741ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:16:39Z" - latency: 2.214635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:16:39Z" kind: List metadata: resourceVersion: ""