apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "55491" uid: 094c7a90-984b-413a-9ee6-d1d06f1b3c85 spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T23:12:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.534µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 982.593µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 1.002088ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 886.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 802.89µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:39Z" - latency: 903.167µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:39Z" - latency: 739.926µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:39Z" - latency: 1.025239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:39Z" - latency: 933.244µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:39Z" - latency: 779.395µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "56461" uid: 391c62a1-e70e-4a00-b5be-e434b4b1905a spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:11:39Z" message: 'load-balancer-api-external: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.130198ms message: 'load-balancer-api-external: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:39Z" - latency: 6.973427ms message: 'load-balancer-api-external: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:41:39Z" - latency: 3.838811ms message: 'load-balancer-api-external: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 8.867904ms message: 'load-balancer-api-external: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:40:39Z" - latency: 4.96237ms message: 'load-balancer-api-external: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 6.31612ms message: 'load-balancer-api-external: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:39:39Z" - latency: 3.891075ms message: 'load-balancer-api-external: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 7.148029ms message: 'load-balancer-api-external: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:38:39Z" - latency: 5.374161ms message: 'load-balancer-api-external: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 7.006081ms message: 'load-balancer-api-external: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:37:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "56462" uid: a3ea0aff-7945-4f3f-96cf-f1b2552ec5b1 spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:11:39Z" message: 'load-balancer-api-internal: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.036241ms message: 'load-balancer-api-internal: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:39Z" - latency: 6.987164ms message: 'load-balancer-api-internal: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:41:39Z" - latency: 3.906509ms message: 'load-balancer-api-internal: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 8.786465ms message: 'load-balancer-api-internal: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:40:39Z" - latency: 3.48752ms message: 'load-balancer-api-internal: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 6.259132ms message: 'load-balancer-api-internal: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:39:39Z" - latency: 4.011802ms message: 'load-balancer-api-internal: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 7.172617ms message: 'load-balancer-api-internal: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:38:39Z" - latency: 5.377986ms message: 'load-balancer-api-internal: tcp connection to a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 6.927602ms message: 'load-balancer-api-internal: resolved host name a08d5391ebba64ed7946301ae0d561bf-a62b1d1f79836858.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:37:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-ip-10-0-132-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "55488" uid: 4b52bff8-c1cf-4000-a061-cdd63941ae0a spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:12:39Z" message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.076622ms message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 810.456µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 746.14µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 927.331µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 728.266µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:39Z" - latency: 1.000945ms message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:39Z" - latency: 895.972µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:39Z" - latency: 966.856µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:39Z" - latency: 901.504µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:39Z" - latency: 838.925µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-ip-10-0-136-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "55490" uid: c8e4c926-c48a-4332-9610-c377670c196c spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:12:39Z" message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.532719ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 2.153132ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 1.966316ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 2.406352ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 1.995641ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:39Z" - latency: 2.454441ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:39Z" - latency: 1.998456ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:39Z" - latency: 2.441859ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:39Z" - latency: 2.409061ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:39Z" - latency: 2.285456ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-ip-10-0-142-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "55489" uid: af25aa94-a369-4768-ad15-108e71d18e45 spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:12:39Z" message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.408491ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 2.058852ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 2.259727ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 2.454339ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 1.864109ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:39Z" - latency: 2.420876ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:39Z" - latency: 2.880258ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:39Z" - latency: 2.794741ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:39Z" - latency: 2.385815ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:39Z" - latency: 2.333655ms message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:05:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 7d2911ec-6cbc-4821-a0f8-6cfe66bfc750 resourceVersion: "56460" uid: b104acd5-5e73-4888-aebf-667e57db76a3 spec: sourcePod: network-check-source-989f8b8dc-srqvx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T23:11:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.756µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:39Z" - latency: 1.85864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:41:39Z" - latency: 771.59µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:39Z" - latency: 1.536239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:40:39Z" - latency: 1.189378ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:39Z" - latency: 1.653926ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:39:39Z" - latency: 1.018939ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:39Z" - latency: 2.128876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:38:39Z" - latency: 802.136µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:39Z" - latency: 1.729537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:37:39Z" kind: List metadata: resourceVersion: ""