apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "69779" uid: 4ad96bef-d30a-44fa-ac4f-d0995373b642 spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T20:51:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.109905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 1.64076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 1.011257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 1.053888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 926.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:15:35Z" - latency: 1.077207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:14:35Z" - latency: 936.021µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:13:35Z" - latency: 1.030118ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:12:35Z" - latency: 986.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:11:35Z" - latency: 771.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "70727" uid: d792a768-4fa0-4fc5-a252-e598e031df7d spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T20:50:35Z" message: 'load-balancer-api-external: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.546619ms message: 'load-balancer-api-external: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:20:35Z" - latency: 8.506587ms message: 'load-balancer-api-external: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:20:35Z" - latency: 4.77296ms message: 'load-balancer-api-external: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 6.699568ms message: 'load-balancer-api-external: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:19:35Z" - latency: 5.157805ms message: 'load-balancer-api-external: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 8.08902ms message: 'load-balancer-api-external: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:18:35Z" - latency: 5.122638ms message: 'load-balancer-api-external: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 7.381551ms message: 'load-balancer-api-external: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:17:35Z" - latency: 4.477465ms message: 'load-balancer-api-external: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 9.851043ms message: 'load-balancer-api-external: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:16:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "70726" uid: 23f0498b-2b84-4b44-ab96-6269fa9eb6df spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T20:50:35Z" message: 'load-balancer-api-internal: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.636761ms message: 'load-balancer-api-internal: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:20:35Z" - latency: 8.436352ms message: 'load-balancer-api-internal: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:20:35Z" - latency: 4.769969ms message: 'load-balancer-api-internal: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 6.743271ms message: 'load-balancer-api-internal: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:19:35Z" - latency: 5.167292ms message: 'load-balancer-api-internal: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 7.971101ms message: 'load-balancer-api-internal: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:18:35Z" - latency: 4.107518ms message: 'load-balancer-api-internal: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 7.489865ms message: 'load-balancer-api-internal: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:17:35Z" - latency: 3.880961ms message: 'load-balancer-api-internal: tcp connection to a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 9.802844ms message: 'load-balancer-api-internal: resolved host name a9be37d35de6b4b99926ffdf0a59affd-1becb99d28dc28bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:16:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-ip-10-0-130-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "69778" uid: 91f1a1d1-6631-4573-a16d-b7f351e29587 spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T20:51:35Z" message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.404708ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 2.76148ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 2.598095ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 2.413195ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 2.450993ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:15:35Z" - latency: 2.733272ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:14:35Z" - latency: 2.433167ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:13:35Z" - latency: 2.050545ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:12:35Z" - latency: 2.472515ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:11:35Z" - latency: 1.883827ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-ip-10-0-138-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "69777" uid: 8f706d30-953c-496f-b37c-dc329d550a76 spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T20:51:35Z" message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.335617ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 2.59678ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 2.625161ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 2.557283ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 2.363225ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:15:35Z" - latency: 2.654753ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:14:35Z" - latency: 2.393413ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:13:35Z" - latency: 2.277929ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:12:35Z" - latency: 2.291177ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:11:35Z" - latency: 2.302385ms message: 'network-check-target-ip-10-0-138-122: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-ip-10-0-139-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "69776" uid: 34af5e48-7a58-438e-89b2-7f1aea4b1d18 spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T20:51:35Z" message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.319666ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 953.275µs message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 1.617792ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 1.176034ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 890.054µs message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:15:35Z" - latency: 1.014162ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:14:35Z" - latency: 1.145349ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:13:35Z" - latency: 964.176µs message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:12:35Z" - latency: 1.170686ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:11:35Z" - latency: 1.183356ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:44:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: e8a54878-add8-4981-b419-f99e60e73c0a resourceVersion: "70725" uid: c71009f0-65f1-45a8-927d-ef8120913d09 spec: sourcePod: network-check-source-6f8b768455-2rjq6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T20:50:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.364428ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:20:35Z" - latency: 1.683192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:20:35Z" - latency: 1.002313ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:19:35Z" - latency: 1.727069ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:19:35Z" - latency: 1.010608ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:18:35Z" - latency: 1.864322ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:18:35Z" - latency: 1.54918ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:17:35Z" - latency: 1.934955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:17:35Z" - latency: 910.729µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:16:35Z" - latency: 1.880647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:16:35Z" kind: List metadata: resourceVersion: ""