apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64850" uid: 5c91b7af-9661-4200-99db-addb06ade511 spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T04:39:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.685µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 917.586µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 880.23µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 938.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 1.298687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 1.182872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:21Z" - latency: 821.026µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:08:21Z" - latency: 1.144272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:07:21Z" - latency: 1.144762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:06:21Z" - latency: 1.19001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:05:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64852" uid: 17d175e5-2730-4fe8-8da4-b6ace4341af5 spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T04:38:21Z" message: 'load-balancer-api-external: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.430397ms message: 'load-balancer-api-external: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 8.854378ms message: 'load-balancer-api-external: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:14:21Z" - latency: 4.68653ms message: 'load-balancer-api-external: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 6.457447ms message: 'load-balancer-api-external: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:13:21Z" - latency: 4.648686ms message: 'load-balancer-api-external: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 8.767591ms message: 'load-balancer-api-external: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:12:21Z" - latency: 3.713445ms message: 'load-balancer-api-external: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 8.04707ms message: 'load-balancer-api-external: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:11:21Z" - latency: 5.670221ms message: 'load-balancer-api-external: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 10.334331ms message: 'load-balancer-api-external: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:10:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64851" uid: c478baba-2ccc-4e84-8852-1adedf5815af spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T04:38:21Z" message: 'load-balancer-api-internal: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.372477ms message: 'load-balancer-api-internal: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 8.846973ms message: 'load-balancer-api-internal: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:14:21Z" - latency: 4.713878ms message: 'load-balancer-api-internal: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 6.503691ms message: 'load-balancer-api-internal: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:13:21Z" - latency: 4.144504ms message: 'load-balancer-api-internal: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 8.834861ms message: 'load-balancer-api-internal: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:12:21Z" - latency: 3.677597ms message: 'load-balancer-api-internal: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 8.142644ms message: 'load-balancer-api-internal: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:11:21Z" - latency: 3.696717ms message: 'load-balancer-api-internal: tcp connection to aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 10.378713ms message: 'load-balancer-api-internal: resolved host name aadad0efe0bda4f8d823e4abdd6acdcc-b0eae8870a039ab8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:10:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-network-check-target-ip-10-0-131-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64849" uid: 1df1fe67-d48f-4388-9541-48f2c3ff9666 spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T04:39:21Z" message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.988168ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 1.698707ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 1.946996ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 2.026529ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 1.972743ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 2.232519ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:21Z" - latency: 1.746428ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:08:21Z" - latency: 2.065714ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:07:21Z" - latency: 2.09324ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:06:21Z" - latency: 1.729091ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:05:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-network-check-target-ip-10-0-141-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64846" uid: 162602cc-707c-4e27-b981-d10340c9b395 spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T04:39:21Z" message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041582ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 2.003088ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 1.84316ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 2.157933ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 2.011967ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 2.207399ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:21Z" - latency: 1.887967ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:08:21Z" - latency: 2.113097ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:07:21Z" - latency: 2.548461ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:06:21Z" - latency: 2.20618ms message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:05:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-network-check-target-ip-10-0-142-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64847" uid: 5ee3970d-22f7-4220-a4eb-63be1b6d204f spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T04:39:21Z" message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.542µs message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 868.637µs message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 1.01376ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 1.339727ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 1.101098ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 877.861µs message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:21Z" - latency: 815.305µs message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:08:21Z" - latency: 710.312µs message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:07:21Z" - latency: 908.018µs message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:06:21Z" - latency: 1.326844ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:05:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:32:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-182-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-182.ec2.internal uid: 0623badb-684b-49f9-b3bc-23255e493ee0 resourceVersion: "64848" uid: e00fbda2-e3f8-48d1-8d2d-0f05eed3cab7 spec: sourcePod: network-check-source-7bc5b6bf85-tb6cw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T04:38:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.092943ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:21Z" - latency: 1.961374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:14:21Z" - latency: 923.152µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:21Z" - latency: 1.707986ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:13:21Z" - latency: 922.177µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:21Z" - latency: 1.866711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:12:21Z" - latency: 1.111349ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:21Z" - latency: 1.607065ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:11:21Z" - latency: 766.646µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:21Z" - latency: 1.881237ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:10:21Z" kind: List metadata: resourceVersion: ""