apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "20598" uid: 73b7ece3-3407-43dd-b4e8-64589dfdcc79 spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T12:07:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.293631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 2.929071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 1.509895ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 1.268528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:25:19Z" - latency: 1.402503ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:24:19Z" - latency: 1.471305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:23:19Z" - latency: 1.542807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:22:19Z" - latency: 983.595µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:21:19Z" - latency: 1.257098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:20:19Z" - latency: 1.590234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "21246" uid: 63accd4a-fab2-44ba-81ac-2cf79281f88e spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T12:06:19Z" message: 'load-balancer-api-external: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.275536ms message: 'load-balancer-api-external: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:30:19Z" - latency: 7.474811ms message: 'load-balancer-api-external: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:30:19Z" - latency: 56.285946ms message: 'load-balancer-api-external: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:29:19Z" - latency: 6.651421ms message: 'load-balancer-api-external: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:29:19Z" - latency: 50.084966ms message: 'load-balancer-api-external: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 6.551711ms message: 'load-balancer-api-external: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:28:19Z" - latency: 51.12785ms message: 'load-balancer-api-external: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 9.700658ms message: 'load-balancer-api-external: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:27:19Z" - latency: 56.71082ms message: 'load-balancer-api-external: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 7.774604ms message: 'load-balancer-api-external: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:26:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "21245" uid: b80c5171-803f-44af-ba07-22cab31f1c58 spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T12:06:19Z" message: 'load-balancer-api-internal: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.249565ms message: 'load-balancer-api-internal: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:30:19Z" - latency: 7.436732ms message: 'load-balancer-api-internal: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:30:19Z" - latency: 56.321263ms message: 'load-balancer-api-internal: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:29:19Z" - latency: 6.635705ms message: 'load-balancer-api-internal: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:29:19Z" - latency: 50.093052ms message: 'load-balancer-api-internal: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 6.513785ms message: 'load-balancer-api-internal: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:28:19Z" - latency: 51.110967ms message: 'load-balancer-api-internal: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 9.80179ms message: 'load-balancer-api-internal: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:27:19Z" - latency: 56.750778ms message: 'load-balancer-api-internal: tcp connection to a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 7.798676ms message: 'load-balancer-api-internal: resolved host name a4fd3b4dc17784092bd3ff428f9e18b0-52a7abf2d90d3fc5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T12:26:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-129-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "20595" uid: 568549fa-0070-4f09-a4f3-7d3dc92b2dfa spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:07:19Z" message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.313959ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 2.305994ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 2.287566ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 2.241406ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:25:19Z" - latency: 2.211583ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:24:19Z" - latency: 2.274252ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:23:19Z" - latency: 3.102974ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:22:19Z" - latency: 2.309048ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:21:19Z" - latency: 2.191291ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:20:19Z" - latency: 2.071484ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-133-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "20594" uid: a0bb3176-74b4-42e1-a20d-a3caefc2a9b0 spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:07:19Z" message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.571µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 3.659013ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 1.129801ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 920.886µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:25:19Z" - latency: 837.206µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:24:19Z" - latency: 1.168487ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:23:19Z" - latency: 2.056884ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:22:19Z" - latency: 933.646µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:21:19Z" - latency: 1.007332ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:20:19Z" - latency: 942.816µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-142-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "20597" uid: 06af2bc9-5774-4ec4-b0ff-b64e04ae8ed4 spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:07:19Z" message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.352774ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 2.706238ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 2.150982ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 1.774583ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:25:19Z" - latency: 2.231863ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:24:19Z" - latency: 2.729818ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:23:19Z" - latency: 3.041745ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:22:19Z" - latency: 2.271405ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:21:19Z" - latency: 2.032746ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:20:19Z" - latency: 1.721188ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:00:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.us-west-2.compute.internal uid: dcf25bf0-dbf6-4ffa-a8bb-0bc4996be7e4 resourceVersion: "21244" uid: e50c7f3c-a0bc-4188-877b-996a8e1fddc6 spec: sourcePod: network-check-source-6f78d59f99-zp9df targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T12:06:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.363µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:30:19Z" - latency: 1.788729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T12:30:19Z" - latency: 853.559µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:29:19Z" - latency: 1.906233ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T12:29:19Z" - latency: 1.021962ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:28:19Z" - latency: 1.921855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T12:28:19Z" - latency: 917.154µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:27:19Z" - latency: 4.567337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T12:27:19Z" - latency: 891.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T12:26:19Z" - latency: 2.584216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T12:26:19Z" kind: List metadata: resourceVersion: ""