apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "19929" uid: bebdd912-1955-4d6e-96f3-70de5f0ad70c spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T02:12:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 837.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 1.156962ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 1.002147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:24:01Z" - latency: 746.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:23:01Z" - latency: 860.938µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:22:01Z" - latency: 839.6µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:21:01Z" - latency: 1.588517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:20:01Z" - latency: 814.662µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:19:01Z" - latency: 1.938645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:18:01Z" - latency: 901.981µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "21090" uid: 9515c116-981d-4a73-999f-8ef7e03251c4 spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T02:11:01Z" message: 'load-balancer-api-external: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.036762ms message: 'load-balancer-api-external: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:29:01Z" - latency: 6.535473ms message: 'load-balancer-api-external: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:29:01Z" - latency: 4.083836ms message: 'load-balancer-api-external: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:28:01Z" - latency: 7.369053ms message: 'load-balancer-api-external: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:28:01Z" - latency: 4.622159ms message: 'load-balancer-api-external: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:27:01Z" - latency: 6.809728ms message: 'load-balancer-api-external: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:27:01Z" - latency: 5.728922ms message: 'load-balancer-api-external: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 8.130172ms message: 'load-balancer-api-external: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:26:01Z" - latency: 3.864187ms message: 'load-balancer-api-external: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 6.557725ms message: 'load-balancer-api-external: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:25:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "21089" uid: 15ac471c-275f-4117-9ced-334f58c9d86d spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T02:11:01Z" message: 'load-balancer-api-internal: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.973579ms message: 'load-balancer-api-internal: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:29:01Z" - latency: 6.609563ms message: 'load-balancer-api-internal: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:29:01Z" - latency: 4.107677ms message: 'load-balancer-api-internal: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:28:01Z" - latency: 7.42604ms message: 'load-balancer-api-internal: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:28:01Z" - latency: 4.590194ms message: 'load-balancer-api-internal: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:27:01Z" - latency: 7.366852ms message: 'load-balancer-api-internal: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:27:01Z" - latency: 5.498604ms message: 'load-balancer-api-internal: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 8.088084ms message: 'load-balancer-api-internal: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:26:01Z" - latency: 4.394304ms message: 'load-balancer-api-internal: tcp connection to a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 6.595365ms message: 'load-balancer-api-internal: resolved host name a7a382c02434e489282a9aafec080965-76f3da94e44fc054.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T02:25:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-network-check-target-ip-10-0-128-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "19926" uid: 8bfe89fd-8501-4b8c-83eb-d6d71a0dfb0d spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T02:12:01Z" message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.703µs message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 1.024433ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 739.815µs message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:24:01Z" - latency: 1.016693ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:23:01Z" - latency: 680.16µs message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:22:01Z" - latency: 807.268µs message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:21:01Z" - latency: 778.391µs message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:20:01Z" - latency: 1.016624ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:19:01Z" - latency: 883.174µs message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:18:01Z" - latency: 1.068839ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-network-check-target-ip-10-0-138-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "19927" uid: ce89c768-fd86-4745-9883-32e87fb78a40 spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-27T02:12:01Z" message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.429239ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 2.326467ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 2.020587ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:24:01Z" - latency: 2.239371ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:23:01Z" - latency: 1.672212ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:22:01Z" - latency: 2.10156ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:21:01Z" - latency: 2.204042ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:20:01Z" - latency: 2.46198ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:19:01Z" - latency: 2.363969ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:18:01Z" - latency: 2.295796ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-network-check-target-ip-10-0-142-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "19928" uid: c5ddff5e-a240-4ed4-a59b-aef0b18668bd spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-27T02:12:01Z" message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363412ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 2.09557ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 2.21075ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:24:01Z" - latency: 2.034018ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:23:01Z" - latency: 1.97176ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:22:01Z" - latency: 2.63574ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:21:01Z" - latency: 2.243571ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:20:01Z" - latency: 2.11248ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:19:01Z" - latency: 1.980545ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:18:01Z" - latency: 2.256081ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T02:05:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-250.ec2.internal uid: f14cecd7-e15d-46a1-b09b-59b75bfbe387 resourceVersion: "21088" uid: 97c3313a-17ff-4c1b-b9ad-cd201ea99201 spec: sourcePod: network-check-source-7f44b6dd87-lkv8h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T02:11:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.97µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:29:01Z" - latency: 1.712585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T02:29:01Z" - latency: 1.110416ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:28:01Z" - latency: 2.044171ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T02:28:01Z" - latency: 839.454µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:27:01Z" - latency: 1.652692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T02:27:01Z" - latency: 862.579µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:26:01Z" - latency: 1.771216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T02:26:01Z" - latency: 1.258271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T02:25:01Z" - latency: 1.786572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T02:25:01Z" kind: List metadata: resourceVersion: ""