apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "85032" uid: f338f5e5-cff2-43b7-9993-c3ebbcb85950 spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T17:23:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.281µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:19:37Z" - latency: 1.526037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:37Z" - latency: 767.298µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:37Z" - latency: 965.716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 944.238µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 1.002081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 1.243299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 804.878µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 871.542µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:37Z" - latency: 965.94µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "82132" uid: 8dc6fe58-35e5-4ffd-ad83-7bbb0fb9bb5f spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:22:37Z" message: 'load-balancer-api-external: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.005985ms message: 'load-balancer-api-external: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 8.515692ms message: 'load-balancer-api-external: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:16:37Z" - latency: 5.370044ms message: 'load-balancer-api-external: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 8.700258ms message: 'load-balancer-api-external: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:15:37Z" - latency: 5.721915ms message: 'load-balancer-api-external: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 8.267162ms message: 'load-balancer-api-external: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:14:37Z" - latency: 4.997518ms message: 'load-balancer-api-external: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 8.074148ms message: 'load-balancer-api-external: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:13:37Z" - latency: 5.645897ms message: 'load-balancer-api-external: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 7.725979ms message: 'load-balancer-api-external: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:12:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "82131" uid: 97e9a6d5-5f4f-4dc3-afb9-f53e7392aad1 spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:22:37Z" message: 'load-balancer-api-internal: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.692828ms message: 'load-balancer-api-internal: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 8.438734ms message: 'load-balancer-api-internal: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:16:37Z" - latency: 5.52021ms message: 'load-balancer-api-internal: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 8.663005ms message: 'load-balancer-api-internal: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:15:37Z" - latency: 5.70152ms message: 'load-balancer-api-internal: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 8.388921ms message: 'load-balancer-api-internal: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:14:37Z" - latency: 5.20727ms message: 'load-balancer-api-internal: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 8.01332ms message: 'load-balancer-api-internal: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:13:37Z" - latency: 5.503426ms message: 'load-balancer-api-internal: tcp connection to a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 7.753383ms message: 'load-balancer-api-internal: resolved host name a485e0620578e4f0aa10383cd56a8f13-1bd207d3aefa6667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:12:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-network-check-target-ip-10-0-131-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "85029" uid: b73b6b93-2fa0-4186-a098-de05d7628b6f spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:23:37Z" message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.593µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:19:37Z" - latency: 833.347µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:37Z" - latency: 841.9µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:37Z" - latency: 1.14571ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 997.259µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 814.025µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 866.034µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 702.42µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 1.100824ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:37Z" - latency: 814.267µs message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-network-check-target-ip-10-0-135-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "85031" uid: de327958-a6eb-4525-9ac1-521feba0cc81 spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:23:37Z" message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.205937ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:19:37Z" - latency: 2.257733ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:37Z" - latency: 2.322132ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:37Z" - latency: 2.226225ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 3.062151ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 2.379563ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 2.004992ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 2.55776ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 2.8198ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:37Z" - latency: 2.238639ms message: 'network-check-target-ip-10-0-135-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-network-check-target-ip-10-0-141-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "85030" uid: bbd0bddf-0e3e-44b2-9f4b-223f54b69d97 spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:23:37Z" message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.160125ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:19:37Z" - latency: 1.993388ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:37Z" - latency: 2.156534ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:37Z" - latency: 2.183211ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 2.075578ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 2.70054ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 1.901759ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 2.05385ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 2.17156ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:37Z" - latency: 1.762789ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:16:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-218-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-218.ec2.internal uid: 46ce8b2c-7cd2-4294-86cc-e26d0919521f resourceVersion: "82129" uid: aa6d3f3f-d1fc-463b-aabe-4f6f731dfb9a spec: sourcePod: network-check-source-65bdbbff45-j22bh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T17:22:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.92µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:37Z" - latency: 1.798215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:16:37Z" - latency: 908.196µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:37Z" - latency: 1.690585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:15:37Z" - latency: 1.050253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:37Z" - latency: 1.845446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:14:37Z" - latency: 868.76µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:37Z" - latency: 1.724792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:13:37Z" - latency: 1.254894ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:37Z" - latency: 1.589686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:12:37Z" kind: List metadata: resourceVersion: ""