apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "42645" uid: 8cd9ff63-fa56-4906-a2fe-5923b5db6dac spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T16:48:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 912.413µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 1.058063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 1.084937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:06:15Z" - latency: 1.129567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:05:15Z" - latency: 1.18707ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:04:15Z" - latency: 1.042364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:03:15Z" - latency: 933.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:02:15Z" - latency: 1.385524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:01:15Z" - latency: 1.020858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "45106" uid: 37fde6f3-6c39-44e0-ae60-02c5ef8d819a spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T16:47:15Z" message: 'load-balancer-api-external: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.656453ms message: 'load-balancer-api-external: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:11:15Z" - latency: 7.875177ms message: 'load-balancer-api-external: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:11:15Z" - latency: 4.681639ms message: 'load-balancer-api-external: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:10:15Z" - latency: 8.560147ms message: 'load-balancer-api-external: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:10:15Z" - latency: 8.979409ms message: 'load-balancer-api-external: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 8.112723ms message: 'load-balancer-api-external: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:09:15Z" - latency: 5.017406ms message: 'load-balancer-api-external: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 8.156541ms message: 'load-balancer-api-external: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:08:15Z" - latency: 6.916605ms message: 'load-balancer-api-external: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 6.935141ms message: 'load-balancer-api-external: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:07:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "45105" uid: 8243b817-6ac6-4740-8c98-616259585238 spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T16:47:15Z" message: 'load-balancer-api-internal: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.697655ms message: 'load-balancer-api-internal: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:11:15Z" - latency: 7.854217ms message: 'load-balancer-api-internal: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:11:15Z" - latency: 3.877416ms message: 'load-balancer-api-internal: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:10:15Z" - latency: 8.521909ms message: 'load-balancer-api-internal: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:10:15Z" - latency: 16.085495ms message: 'load-balancer-api-internal: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 8.158612ms message: 'load-balancer-api-internal: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:09:15Z" - latency: 4.862195ms message: 'load-balancer-api-internal: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 8.139879ms message: 'load-balancer-api-internal: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:08:15Z" - latency: 7.734018ms message: 'load-balancer-api-internal: tcp connection to ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 6.96841ms message: 'load-balancer-api-internal: resolved host name ad0441dfc484a4df6a8ce0c5a9f71b9a-d7d70866a77f4067.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T17:07:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-network-check-target-ip-10-0-133-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "42643" uid: 3272363b-af4b-4386-ac31-9fcc555042fe spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T16:48:15Z" message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.023052ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 1.860178ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 1.950756ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 2.031925ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:06:15Z" - latency: 2.053012ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:05:15Z" - latency: 1.904836ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:04:15Z" - latency: 1.90113ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:03:15Z" - latency: 1.980846ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:02:15Z" - latency: 1.917451ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:01:15Z" - latency: 1.856478ms message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-network-check-target-ip-10-0-135-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "42644" uid: 675caef8-9f42-4a7d-a3e7-bc365cfc4b27 spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T16:48:15Z" message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.651µs message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 1.186237ms message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 1.234634ms message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 944.971µs message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:06:15Z" - latency: 1.002536ms message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:05:15Z" - latency: 1.321429ms message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:04:15Z" - latency: 954.454µs message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:03:15Z" - latency: 1.254561ms message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:02:15Z" - latency: 790.707µs message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:01:15Z" - latency: 716.1µs message: 'network-check-target-ip-10-0-135-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-network-check-target-ip-10-0-140-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "42642" uid: 2606b801-8072-42af-ad3d-1d5e8c7c636f spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T16:48:15Z" message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.911057ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 2.018349ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 2.12601ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 2.278185ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:06:15Z" - latency: 2.318966ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:05:15Z" - latency: 2.211904ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:04:15Z" - latency: 2.095671ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:03:15Z" - latency: 2.052081ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:02:15Z" - latency: 1.924692ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:01:15Z" - latency: 2.45841ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T16:41:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-137-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-137.ec2.internal uid: e20e0a6d-55d6-40f5-b440-9c5cc884bc68 resourceVersion: "45104" uid: 5fd237ef-f54f-49f4-a431-674c3dedd303 spec: sourcePod: network-check-source-7f44b6dd87-xx9hh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T16:47:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 789.305µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:11:15Z" - latency: 1.541549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T17:11:15Z" - latency: 1.13625ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:10:15Z" - latency: 1.755712ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T17:10:15Z" - latency: 652.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:09:15Z" - latency: 1.908196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T17:09:15Z" - latency: 797.412µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:08:15Z" - latency: 1.701049ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T17:08:15Z" - latency: 874.574µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T17:07:15Z" - latency: 1.984387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T17:07:15Z" kind: List metadata: resourceVersion: ""