apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62173" uid: 36adb38f-00bd-4f08-87a5-7462fafce7c0 spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T13:26:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.410722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 1.620674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 840.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 1.252016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 962.783µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 1.333478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:56:02Z" - latency: 1.353619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:02Z" - latency: 849.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:02Z" - latency: 1.092427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:02Z" - latency: 1.087993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62175" uid: 7f61343b-d220-432a-8764-23b0cd9dba49 spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T13:25:02Z" message: 'load-balancer-api-external: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.563515ms message: 'load-balancer-api-external: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 8.58767ms message: 'load-balancer-api-external: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T14:01:02Z" - latency: 4.680489ms message: 'load-balancer-api-external: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 8.342767ms message: 'load-balancer-api-external: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T14:00:02Z" - latency: 5.862994ms message: 'load-balancer-api-external: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 8.549465ms message: 'load-balancer-api-external: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:59:02Z" - latency: 5.707945ms message: 'load-balancer-api-external: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 7.426671ms message: 'load-balancer-api-external: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:58:02Z" - latency: 5.794582ms message: 'load-balancer-api-external: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 9.403967ms message: 'load-balancer-api-external: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:57:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62176" uid: 61f1bbdd-c2a6-466d-9958-fcca71c58f8e spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T13:25:02Z" message: 'load-balancer-api-internal: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.507285ms message: 'load-balancer-api-internal: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 8.64929ms message: 'load-balancer-api-internal: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T14:01:02Z" - latency: 4.674188ms message: 'load-balancer-api-internal: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 8.380572ms message: 'load-balancer-api-internal: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T14:00:02Z" - latency: 5.881932ms message: 'load-balancer-api-internal: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 8.481836ms message: 'load-balancer-api-internal: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:59:02Z" - latency: 5.653689ms message: 'load-balancer-api-internal: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 7.334913ms message: 'load-balancer-api-internal: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:58:02Z" - latency: 5.808986ms message: 'load-balancer-api-internal: tcp connection to a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 9.323428ms message: 'load-balancer-api-internal: resolved host name a82991101df0e40ec82a164e53bbc8e1-003f3945f94f2e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:57:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-network-check-target-ip-10-0-128-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62169" uid: f9f62e3a-5469-497b-8e9b-b02050f2c865 spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T13:26:02Z" message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.826748ms message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 1.499601ms message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 1.029245ms message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 1.261544ms message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 1.003152ms message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 859.866µs message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:56:02Z" - latency: 984.407µs message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:02Z" - latency: 882.507µs message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:02Z" - latency: 1.308557ms message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:02Z" - latency: 921.683µs message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-network-check-target-ip-10-0-132-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62170" uid: 2fc5cbf0-4b1d-4c8e-9bf3-44ab9e6ab44a spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T13:26:02Z" message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.224835ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 2.124893ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 1.732231ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 2.060465ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 1.935795ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 1.901309ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:56:02Z" - latency: 1.970828ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:02Z" - latency: 1.910957ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:02Z" - latency: 2.028615ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:02Z" - latency: 1.896074ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-network-check-target-ip-10-0-136-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62171" uid: b76b9d67-1605-4aa7-bc44-bb82f50da1c8 spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T13:26:02Z" message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.311564ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 2.626554ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 2.159874ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 2.22552ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 2.42994ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 2.80248ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:56:02Z" - latency: 2.245847ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:02Z" - latency: 2.085597ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:02Z" - latency: 2.32827ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:02Z" - latency: 2.212814ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:19:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-159-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-159.ec2.internal uid: 87266a78-37d6-4e00-a543-7213f9b72300 resourceVersion: "62172" uid: dd527dc1-a67b-4036-9506-5588b4f830ed spec: sourcePod: network-check-source-869dcfcdcd-jzfn9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T13:25:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.433154ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:01:02Z" - latency: 1.732511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T14:01:02Z" - latency: 1.053336ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T14:00:02Z" - latency: 2.183726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T14:00:02Z" - latency: 923.693µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:59:02Z" - latency: 1.763977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:59:02Z" - latency: 853.881µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:58:02Z" - latency: 2.144293ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:58:02Z" - latency: 773.166µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:57:02Z" - latency: 2.511556ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:57:02Z" kind: List metadata: resourceVersion: ""