apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "46618" uid: 0b8a0388-a9a3-4217-a9ff-1e72c920cfc0 spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T15:06:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.781174ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 933.858µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 833.791µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 927.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:24:28Z" - latency: 1.129763ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:23:28Z" - latency: 1.098203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:22:28Z" - latency: 1.468534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:21:28Z" - latency: 1.036143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:20:28Z" - latency: 928.146µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:19:28Z" - latency: 1.078139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "49273" uid: 7a98ff90-1baa-48d7-aa4c-d0f0697cac2b spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:05:28Z" message: 'load-balancer-api-external: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.512477ms message: 'load-balancer-api-external: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:29:28Z" - latency: 6.528574ms message: 'load-balancer-api-external: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:29:28Z" - latency: 4.57733ms message: 'load-balancer-api-external: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:28:28Z" - latency: 6.902681ms message: 'load-balancer-api-external: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:28:28Z" - latency: 5.220249ms message: 'load-balancer-api-external: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 6.524562ms message: 'load-balancer-api-external: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:27:28Z" - latency: 5.362382ms message: 'load-balancer-api-external: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 7.286112ms message: 'load-balancer-api-external: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:26:28Z" - latency: 4.741334ms message: 'load-balancer-api-external: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 6.535083ms message: 'load-balancer-api-external: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:25:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "49274" uid: d867b73a-463a-4be7-b151-dab08b2a8486 spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:05:28Z" message: 'load-balancer-api-internal: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.037886ms message: 'load-balancer-api-internal: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:29:28Z" - latency: 6.584701ms message: 'load-balancer-api-internal: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:29:28Z" - latency: 4.572656ms message: 'load-balancer-api-internal: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:28:28Z" - latency: 6.775774ms message: 'load-balancer-api-internal: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:28:28Z" - latency: 5.244084ms message: 'load-balancer-api-internal: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 6.455662ms message: 'load-balancer-api-internal: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:27:28Z" - latency: 4.311573ms message: 'load-balancer-api-internal: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 7.259807ms message: 'load-balancer-api-internal: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:26:28Z" - latency: 4.794798ms message: 'load-balancer-api-internal: tcp connection to a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 6.519032ms message: 'load-balancer-api-internal: resolved host name a18bff90af6074bd0a2abc5c190dd6dd-92babac669e159c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:25:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-network-check-target-ip-10-0-128-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "46616" uid: 5d0620e4-0317-4020-a88a-ca3f757ed71e spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:06:28Z" message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.896574ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 1.912705ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 1.913711ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 1.805571ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:24:28Z" - latency: 2.121345ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:23:28Z" - latency: 2.092281ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:22:28Z" - latency: 2.161329ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:21:28Z" - latency: 1.799204ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:20:28Z" - latency: 2.143416ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:19:28Z" - latency: 2.127812ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-network-check-target-ip-10-0-129-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "46615" uid: a78ff6e9-9057-40fe-9cd3-aaf0fb94d759 spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:06:28Z" message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.100455ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 1.150474ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 832.792µs message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 1.018535ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:24:28Z" - latency: 954.394µs message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:23:28Z" - latency: 949.598µs message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:22:28Z" - latency: 1.459062ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:21:28Z" - latency: 1.201636ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:20:28Z" - latency: 1.30707ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:19:28Z" - latency: 1.336676ms message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-network-check-target-ip-10-0-142-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "46617" uid: 57e55e98-e355-41ba-8095-18d91cd36d13 spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:06:28Z" message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.173142ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 1.931086ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 2.300193ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 2.306918ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:24:28Z" - latency: 2.401322ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:23:28Z" - latency: 2.139868ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:22:28Z" - latency: 2.286511ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:21:28Z" - latency: 1.978572ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:20:28Z" - latency: 2.268387ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:19:28Z" - latency: 2.195636ms message: 'network-check-target-ip-10-0-142-231: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-1-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-1.ec2.internal uid: dbd5ab4e-ac56-432b-9e78-1465537298b2 resourceVersion: "49272" uid: c0eaf0a5-f0c0-4427-b179-84df9491f434 spec: sourcePod: network-check-source-869dcfcdcd-bv46x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T15:05:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.26624ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:29:28Z" - latency: 1.911019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:29:28Z" - latency: 877.424µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:28:28Z" - latency: 1.64485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:28:28Z" - latency: 838.305µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:27:28Z" - latency: 2.063994ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:27:28Z" - latency: 938.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:26:28Z" - latency: 1.878518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:26:28Z" - latency: 852.996µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:25:28Z" - latency: 1.854313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:25:28Z" kind: List metadata: resourceVersion: ""