apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "38835" uid: a102e06b-1585-4ff5-9381-e1694fedaec5 spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:35:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.344825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:24Z" - latency: 986.575µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:24Z" - latency: 1.018005ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:24Z" - latency: 1.144791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:24Z" - latency: 997.952µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 1.065508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 1.12828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 898.636µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 954.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 1.223603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "36289" uid: 2c7e40f6-5a89-4498-b574-9cb5d4b7f7d3 spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:34:24Z" message: 'load-balancer-api-external: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.339493ms message: 'load-balancer-api-external: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 9.388203ms message: 'load-balancer-api-external: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:52:24Z" - latency: 4.175607ms message: 'load-balancer-api-external: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 8.317083ms message: 'load-balancer-api-external: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:51:24Z" - latency: 5.200191ms message: 'load-balancer-api-external: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 8.780686ms message: 'load-balancer-api-external: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:50:24Z" - latency: 5.662991ms message: 'load-balancer-api-external: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 6.919324ms message: 'load-balancer-api-external: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:49:24Z" - latency: 4.658417ms message: 'load-balancer-api-external: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 8.29924ms message: 'load-balancer-api-external: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:48:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "36288" uid: 10504178-bc72-4f60-8e7e-7919b057d938 spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:34:24Z" message: 'load-balancer-api-internal: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.299496ms message: 'load-balancer-api-internal: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 9.346477ms message: 'load-balancer-api-internal: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:52:24Z" - latency: 4.13966ms message: 'load-balancer-api-internal: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 8.252413ms message: 'load-balancer-api-internal: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:51:24Z" - latency: 5.215072ms message: 'load-balancer-api-internal: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 8.718279ms message: 'load-balancer-api-internal: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:50:24Z" - latency: 5.370645ms message: 'load-balancer-api-internal: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 6.884397ms message: 'load-balancer-api-internal: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:49:24Z" - latency: 4.87914ms message: 'load-balancer-api-internal: tcp connection to aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 8.224132ms message: 'load-balancer-api-internal: resolved host name aa068a20331f74ea18ef6f976fd46332-c945280b9a0c89b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:48:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-network-check-target-ip-10-0-133-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "38834" uid: f16d1d33-a8e0-4111-b4e0-373892af7de1 spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:35:24Z" message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.953623ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:24Z" - latency: 2.185733ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:24Z" - latency: 2.360112ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:24Z" - latency: 2.134341ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:24Z" - latency: 2.603834ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 2.187682ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 2.282262ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 2.330976ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 2.086507ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 2.625649ms message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-network-check-target-ip-10-0-139-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "38833" uid: 857a7727-5aa7-4efd-9812-c56f368b8679 spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:35:24Z" message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.785183ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:24Z" - latency: 1.86178ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:24Z" - latency: 1.709639ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:24Z" - latency: 1.784469ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:24Z" - latency: 1.907684ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 1.886306ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 1.812861ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 1.99435ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 1.84047ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 1.680968ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-network-check-target-ip-10-0-143-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "38832" uid: 1a134af6-ad4f-497c-8794-c10b4ac33e6d spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:35:24Z" message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.052066ms message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:24Z" - latency: 1.517506ms message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:24Z" - latency: 816.406µs message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:24Z" - latency: 840.134µs message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:24Z" - latency: 1.101239ms message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 763.627µs message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 874.355µs message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 1.334279ms message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 1.156077ms message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 1.0315ms message: 'network-check-target-ip-10-0-143-59: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-59-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-59.ec2.internal uid: 465a73a7-9c8a-42bd-87e4-8891c7ae5267 resourceVersion: "36287" uid: 6ffc540d-2ec8-4bed-a7f6-e3aea1537de2 spec: sourcePod: network-check-source-8894fc9bd-bgmm8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:34:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.243383ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:24Z" - latency: 2.31868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:52:24Z" - latency: 921.426µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:24Z" - latency: 1.693278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:51:24Z" - latency: 884.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:50:24Z" - latency: 1.835119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:50:24Z" - latency: 973.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:49:24Z" - latency: 1.707769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:49:24Z" - latency: 936.262µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:24Z" - latency: 1.859616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:48:24Z" kind: List metadata: resourceVersion: ""