apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "19615" uid: f0ef5a0f-7002-4e39-a969-069a0ead38e9 spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T03:04:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 1.030838ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 898.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:16:02Z" - latency: 934.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:15:02Z" - latency: 1.25244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:14:02Z" - latency: 982.421µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:13:02Z" - latency: 1.07532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:12:02Z" - latency: 942.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:11:02Z" - latency: 837.232µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:10:02Z" - latency: 1.153383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:09:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "20771" uid: 69e042e0-8051-4c84-9c24-cace06400b93 spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T03:03:02Z" message: 'load-balancer-api-external: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.155154ms message: 'load-balancer-api-external: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:21:02Z" - latency: 7.608674ms message: 'load-balancer-api-external: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:21:02Z" - latency: 3.673255ms message: 'load-balancer-api-external: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:20:02Z" - latency: 7.729538ms message: 'load-balancer-api-external: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:20:02Z" - latency: 4.728861ms message: 'load-balancer-api-external: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:19:02Z" - latency: 8.156871ms message: 'load-balancer-api-external: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:19:02Z" - latency: 5.105575ms message: 'load-balancer-api-external: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 7.495732ms message: 'load-balancer-api-external: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:18:02Z" - latency: 4.040993ms message: 'load-balancer-api-external: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 7.902976ms message: 'load-balancer-api-external: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:17:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "20772" uid: 39bdb4f3-8525-4084-aa3f-c0f10e89fe65 spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T03:03:02Z" message: 'load-balancer-api-internal: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.173144ms message: 'load-balancer-api-internal: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:21:02Z" - latency: 7.677222ms message: 'load-balancer-api-internal: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:21:02Z" - latency: 3.655582ms message: 'load-balancer-api-internal: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:20:02Z" - latency: 7.758018ms message: 'load-balancer-api-internal: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:20:02Z" - latency: 4.724819ms message: 'load-balancer-api-internal: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:19:02Z" - latency: 8.103148ms message: 'load-balancer-api-internal: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:19:02Z" - latency: 5.086619ms message: 'load-balancer-api-internal: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 7.580208ms message: 'load-balancer-api-internal: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:18:02Z" - latency: 4.136367ms message: 'load-balancer-api-internal: tcp connection to ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 8.004881ms message: 'load-balancer-api-internal: resolved host name ac52844cd23214dff951e887b7debe1d-ecf89993c8fe8838.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:17:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-137-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "19613" uid: 8edc3f3f-3de3-45eb-97e7-37dbf935d3fb spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T03:04:02Z" message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.772793ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 1.827908ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 1.740035ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:16:02Z" - latency: 1.975755ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:15:02Z" - latency: 1.803183ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:14:02Z" - latency: 1.597554ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:13:02Z" - latency: 1.946217ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:12:02Z" - latency: 1.87874ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:11:02Z" - latency: 1.87388ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:10:02Z" - latency: 2.001317ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:09:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-138-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "19612" uid: b4af15e5-e1f3-467f-bd7f-34d87f46009b spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T03:04:02Z" message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 774.198µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 980.048µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 935.743µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:16:02Z" - latency: 776.246µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:15:02Z" - latency: 1.378444ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:14:02Z" - latency: 752.145µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:13:02Z" - latency: 1.351478ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:12:02Z" - latency: 772.7µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:11:02Z" - latency: 766.461µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:10:02Z" - latency: 958.627µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:09:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-140-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "19614" uid: ba702882-17fc-4b1b-b934-b86593a79f78 spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T03:04:02Z" message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.074543ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 1.974237ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 1.956272ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:16:02Z" - latency: 1.972466ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:15:02Z" - latency: 1.86499ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:14:02Z" - latency: 2.064638ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:13:02Z" - latency: 2.180669ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:12:02Z" - latency: 2.078743ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:11:02Z" - latency: 1.951935ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:10:02Z" - latency: 2.259272ms message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:09:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:57:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3c8f56d3-a436-44c8-a8da-4533bb3699d7 resourceVersion: "20770" uid: 2d1b0823-af7e-4f2d-995f-1501dbbe9429 spec: sourcePod: network-check-source-7f44b6dd87-q8qcm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T03:03:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 817.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:21:02Z" - latency: 1.674241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:21:02Z" - latency: 1.059177ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:20:02Z" - latency: 1.592413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:20:02Z" - latency: 810.19µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:19:02Z" - latency: 1.599879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:19:02Z" - latency: 978.626µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:18:02Z" - latency: 1.56814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:18:02Z" - latency: 967.408µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:17:02Z" - latency: 1.648033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:17:02Z" kind: List metadata: resourceVersion: ""