apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "54974" uid: 06250605-0f33-45e6-8775-b0ca15032846 spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T19:10:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.063628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 905.944µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 824.751µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 943.035µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 1.169423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:34:21Z" - latency: 1.169532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:33:21Z" - latency: 1.077052ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:32:21Z" - latency: 1.330547ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:31:21Z" - latency: 903.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:30:21Z" - latency: 1.044484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "55998" uid: d7e5b5c7-584f-49e4-902f-3837c03926ea spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T19:09:21Z" message: 'load-balancer-api-external: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.664634ms message: 'load-balancer-api-external: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:39:21Z" - latency: 8.791887ms message: 'load-balancer-api-external: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:39:21Z" - latency: 5.2907ms message: 'load-balancer-api-external: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 7.473159ms message: 'load-balancer-api-external: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:38:21Z" - latency: 3.90389ms message: 'load-balancer-api-external: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 8.667656ms message: 'load-balancer-api-external: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:37:21Z" - latency: 3.487962ms message: 'load-balancer-api-external: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 8.188043ms message: 'load-balancer-api-external: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:36:21Z" - latency: 3.565755ms message: 'load-balancer-api-external: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 9.178001ms message: 'load-balancer-api-external: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:35:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "55999" uid: 21bf2ec2-570f-4229-a4bc-baf63f08b825 spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T19:09:21Z" message: 'load-balancer-api-internal: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.091339ms message: 'load-balancer-api-internal: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:39:21Z" - latency: 8.82052ms message: 'load-balancer-api-internal: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:39:21Z" - latency: 5.098799ms message: 'load-balancer-api-internal: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 7.405502ms message: 'load-balancer-api-internal: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:38:21Z" - latency: 3.814564ms message: 'load-balancer-api-internal: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 8.722692ms message: 'load-balancer-api-internal: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:37:21Z" - latency: 3.49732ms message: 'load-balancer-api-internal: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 8.125938ms message: 'load-balancer-api-internal: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:36:21Z" - latency: 3.296349ms message: 'load-balancer-api-internal: tcp connection to ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 9.139491ms message: 'load-balancer-api-internal: resolved host name ac550dae45e2e463fb8974fed4927177-670c361efe1521fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:35:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-network-check-target-ip-10-0-130-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "54973" uid: 930eb070-e183-459c-95d8-79af0f647688 spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T19:10:21Z" message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.845988ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 1.89925ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 1.71973ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 2.108424ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 2.005611ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:34:21Z" - latency: 2.066665ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:33:21Z" - latency: 1.969909ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:32:21Z" - latency: 1.929226ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:31:21Z" - latency: 1.818562ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:30:21Z" - latency: 2.044729ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-network-check-target-ip-10-0-137-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "54971" uid: 095bc5ee-4a81-4a9d-b906-6d9838968c9c spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T19:10:21Z" message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007722ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 883.367µs message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 1.426171ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 977.032µs message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 1.153809ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:34:21Z" - latency: 885.945µs message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:33:21Z" - latency: 1.981096ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:32:21Z" - latency: 1.87344ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:31:21Z" - latency: 1.541731ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:30:21Z" - latency: 746.639µs message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-network-check-target-ip-10-0-141-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "54972" uid: 632585ad-d85c-4273-8ccf-739cb85fba8d spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T19:10:21Z" message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.911214ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 2.064922ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 2.10878ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 1.983003ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 2.171009ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:34:21Z" - latency: 2.162429ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:33:21Z" - latency: 2.007093ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:32:21Z" - latency: 2.212791ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:31:21Z" - latency: 1.814552ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:30:21Z" - latency: 2.346298ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:03:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-168-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-168.ec2.internal uid: 58973fab-c1f5-4ef2-9a1b-4eb6280a7a0b resourceVersion: "55997" uid: aba53fde-ebb0-4930-9159-998a9a9baf45 spec: sourcePod: network-check-source-869dcfcdcd-9q6bl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T19:09:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.77µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:39:21Z" - latency: 1.881941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:39:21Z" - latency: 845.549µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:38:21Z" - latency: 1.839552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:38:21Z" - latency: 868.259µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:37:21Z" - latency: 1.905614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:37:21Z" - latency: 1.12257ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:36:21Z" - latency: 1.706833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:36:21Z" - latency: 1.037935ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:35:21Z" - latency: 1.814988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:35:21Z" kind: List metadata: resourceVersion: ""