apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "43382" uid: 473e476d-f3b1-4ce4-9775-8d6292895649 spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T16:13:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.228932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 1.238803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 1.638836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 881.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:31:43Z" - latency: 1.195382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:30:43Z" - latency: 1.276404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:29:43Z" - latency: 1.177465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:28:43Z" - latency: 1.189974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:43Z" - latency: 942.458µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:43Z" - latency: 1.267326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "45875" uid: 89e15fd1-f768-4589-87f6-7539a1559a74 spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T16:12:43Z" message: 'load-balancer-api-external: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.455443ms message: 'load-balancer-api-external: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:36:43Z" - latency: 6.944248ms message: 'load-balancer-api-external: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:36:43Z" - latency: 4.990763ms message: 'load-balancer-api-external: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:35:43Z" - latency: 6.59832ms message: 'load-balancer-api-external: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:35:43Z" - latency: 5.528307ms message: 'load-balancer-api-external: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 6.305212ms message: 'load-balancer-api-external: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:34:43Z" - latency: 4.658858ms message: 'load-balancer-api-external: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 6.56411ms message: 'load-balancer-api-external: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:33:43Z" - latency: 4.671469ms message: 'load-balancer-api-external: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 6.805585ms message: 'load-balancer-api-external: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:32:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "45876" uid: 042d71f8-942a-46c8-9594-e4c71f08fb81 spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T16:12:43Z" message: 'load-balancer-api-internal: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.791049ms message: 'load-balancer-api-internal: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:36:43Z" - latency: 6.994677ms message: 'load-balancer-api-internal: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:36:43Z" - latency: 4.990576ms message: 'load-balancer-api-internal: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:35:43Z" - latency: 6.52916ms message: 'load-balancer-api-internal: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:35:43Z" - latency: 5.574928ms message: 'load-balancer-api-internal: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 6.238667ms message: 'load-balancer-api-internal: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:34:43Z" - latency: 3.639469ms message: 'load-balancer-api-internal: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 6.599643ms message: 'load-balancer-api-internal: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:33:43Z" - latency: 4.854941ms message: 'load-balancer-api-internal: tcp connection to aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 6.763233ms message: 'load-balancer-api-internal: resolved host name aa1e1e54e4565497689105319867d247-d6f82ca75242a528.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:32:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-network-check-target-ip-10-0-134-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "43379" uid: 554d92da-ccb8-48c9-8fc1-158cf9d5617b spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T16:13:43Z" message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.194302ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 2.108375ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 2.287353ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 2.267503ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:31:43Z" - latency: 2.169913ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:30:43Z" - latency: 2.056327ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:29:43Z" - latency: 2.424916ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:28:43Z" - latency: 2.093526ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:43Z" - latency: 2.249123ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:43Z" - latency: 2.20843ms message: 'network-check-target-ip-10-0-134-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-network-check-target-ip-10-0-134-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "43380" uid: 9c05ed4b-c9b7-4872-a75f-13022cc56fbc spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T16:13:43Z" message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.7507ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 1.840524ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 1.865046ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 1.726672ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:31:43Z" - latency: 1.854026ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:30:43Z" - latency: 2.002426ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:29:43Z" - latency: 1.762498ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:28:43Z" - latency: 2.077777ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:43Z" - latency: 1.886414ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:43Z" - latency: 1.851472ms message: 'network-check-target-ip-10-0-134-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-network-check-target-ip-10-0-136-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "43381" uid: 876a0a7b-ec30-44fd-b12c-a7249dc13fe7 spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T16:13:43Z" message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.631µs message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 911.665µs message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 1.184436ms message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 1.018696ms message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:31:43Z" - latency: 912.698µs message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:30:43Z" - latency: 964.099µs message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:29:43Z" - latency: 875.264µs message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:28:43Z" - latency: 1.283256ms message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:43Z" - latency: 1.459485ms message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:43Z" - latency: 954.844µs message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-8.ec2.internal uid: 82611237-7f3e-4e49-b1eb-43c8531b8739 resourceVersion: "45874" uid: 1cae57dc-ad6a-4777-9acd-27cb682d62c8 spec: sourcePod: network-check-source-7f44b6dd87-vd8fx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T16:12:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.866µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:36:43Z" - latency: 1.925932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:36:43Z" - latency: 916.841µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:35:43Z" - latency: 1.748626ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:35:43Z" - latency: 832.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:34:43Z" - latency: 1.800669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:34:43Z" - latency: 827.442µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:33:43Z" - latency: 1.879588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:33:43Z" - latency: 952.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:32:43Z" - latency: 1.809252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:32:43Z" kind: List metadata: resourceVersion: ""