apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "70307" uid: 7e60150f-29d7-4988-802c-6945356ae729 spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-18T00:51:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.208978ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:33:55Z" - latency: 1.047754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 846.453µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 967.681µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 957.053µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 1.350569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 962.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:27:55Z" - latency: 1.361861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:55Z" - latency: 1.080594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:55Z" - latency: 1.312944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "69292" uid: 8b9d9ef1-f21e-4220-8d22-726649ffea31 spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T00:50:55Z" message: 'load-balancer-api-external: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.936261ms message: 'load-balancer-api-external: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 6.906136ms message: 'load-balancer-api-external: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:32:55Z" - latency: 4.294228ms message: 'load-balancer-api-external: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 6.709322ms message: 'load-balancer-api-external: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:31:55Z" - latency: 3.96364ms message: 'load-balancer-api-external: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 7.324457ms message: 'load-balancer-api-external: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:30:55Z" - latency: 3.931828ms message: 'load-balancer-api-external: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 6.305837ms message: 'load-balancer-api-external: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:29:55Z" - latency: 5.499191ms message: 'load-balancer-api-external: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 6.423234ms message: 'load-balancer-api-external: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:28:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "69293" uid: b24dad66-60eb-4c6b-ba14-7baa5f61fe61 spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T00:50:55Z" message: 'load-balancer-api-internal: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.942223ms message: 'load-balancer-api-internal: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 6.870269ms message: 'load-balancer-api-internal: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:32:55Z" - latency: 4.310174ms message: 'load-balancer-api-internal: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 6.748214ms message: 'load-balancer-api-internal: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:31:55Z" - latency: 3.650371ms message: 'load-balancer-api-internal: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 7.306357ms message: 'load-balancer-api-internal: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:30:55Z" - latency: 3.929182ms message: 'load-balancer-api-internal: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 6.209316ms message: 'load-balancer-api-internal: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:29:55Z" - latency: 5.491867ms message: 'load-balancer-api-internal: tcp connection to a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 6.37091ms message: 'load-balancer-api-internal: resolved host name a43b3a8ba24034ae4a4ee36fa35a9418-19b88718689ad41b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:28:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-ip-10-0-135-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "70304" uid: d2a23a47-f374-4343-9002-caf1691534cd spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-18T00:51:55Z" message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.534µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:33:55Z" - latency: 861.319µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 797.664µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 827.734µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 755.304µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 739.658µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 840.449µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:27:55Z" - latency: 859.543µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:55Z" - latency: 979.059µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:55Z" - latency: 1.304218ms message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-ip-10-0-141-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "70305" uid: c259b9d4-70fe-44cf-a724-9080ec819c3c spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-18T00:51:55Z" message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.835601ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:33:55Z" - latency: 1.846588ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 3.097428ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 2.22566ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 1.958562ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 2.079286ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 2.061872ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:27:55Z" - latency: 1.913748ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:55Z" - latency: 1.997705ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:55Z" - latency: 2.061363ms message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-ip-10-0-143-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "70306" uid: e4ffc70b-d833-4677-aa8f-79313efe7346 spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-18T00:51:55Z" message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.831034ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:33:55Z" - latency: 2.441762ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 2.341519ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 2.404289ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 2.461756ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 2.116346ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 2.412884ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:27:55Z" - latency: 2.440517ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:55Z" - latency: 2.457049ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:55Z" - latency: 2.507552ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:44:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 6eeb3e39-b489-42d6-9fce-416fe9c82ec9 resourceVersion: "69289" uid: b8e1fb68-986f-40e7-ab8c-f0566f77ab45 spec: sourcePod: network-check-source-7bc5b6bf85-64kzz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-18T00:50:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 840.699µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:32:55Z" - latency: 1.729653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:32:55Z" - latency: 1.38949ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:31:55Z" - latency: 1.750005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:31:55Z" - latency: 907.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:30:55Z" - latency: 1.742006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:30:55Z" - latency: 1.00237ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:29:55Z" - latency: 1.627786ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:29:55Z" - latency: 808.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:28:55Z" - latency: 1.787498ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:28:55Z" kind: List metadata: resourceVersion: ""