apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63377" uid: ced44b3f-0213-4836-846a-f7f5be54f841 spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T01:57:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.160581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 1.245587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 1.207956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 1.159135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 1.290288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 938.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:57Z" - latency: 988.007µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:57Z" - latency: 1.787907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:57Z" - latency: 1.124391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:57Z" - latency: 1.060378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63379" uid: 4c5ef967-262e-47dc-a13b-86f8cdc183de spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:56:57Z" message: 'load-balancer-api-external: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.262217ms message: 'load-balancer-api-external: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 7.142107ms message: 'load-balancer-api-external: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:32:57Z" - latency: 4.675325ms message: 'load-balancer-api-external: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 6.998391ms message: 'load-balancer-api-external: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:31:57Z" - latency: 5.149477ms message: 'load-balancer-api-external: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 6.355205ms message: 'load-balancer-api-external: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:30:57Z" - latency: 4.852655ms message: 'load-balancer-api-external: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 8.123251ms message: 'load-balancer-api-external: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:29:57Z" - latency: 3.413383ms message: 'load-balancer-api-external: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 6.623694ms message: 'load-balancer-api-external: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:28:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63378" uid: 19e6d6d5-d7fc-478e-8af0-30b65763a938 spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:56:57Z" message: 'load-balancer-api-internal: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.965659ms message: 'load-balancer-api-internal: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 7.009919ms message: 'load-balancer-api-internal: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:32:57Z" - latency: 4.666687ms message: 'load-balancer-api-internal: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 6.884405ms message: 'load-balancer-api-internal: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:31:57Z" - latency: 5.16711ms message: 'load-balancer-api-internal: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 6.239749ms message: 'load-balancer-api-internal: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:30:57Z" - latency: 4.686689ms message: 'load-balancer-api-internal: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 7.907576ms message: 'load-balancer-api-internal: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:29:57Z" - latency: 3.387971ms message: 'load-balancer-api-internal: tcp connection to ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 6.645501ms message: 'load-balancer-api-internal: resolved host name ad15ab18f92054c1e8c94109f24f77d7-0c9bb5ea391e7550.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:28:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-network-check-target-ip-10-0-132-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63375" uid: ce3b682f-f842-4859-9962-3983a4c4bb89 spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: 10.135.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:57:57Z" message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299605ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 1.863782ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 2.29333ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 2.207942ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 2.318291ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 2.06013ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:57Z" - latency: 2.217665ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:57Z" - latency: 2.170369ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:57Z" - latency: 1.979184ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:57Z" - latency: 2.127593ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.135.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-network-check-target-ip-10-0-135-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63374" uid: 5cc03e11-621a-4a87-93f8-bacb4c075bc2 spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:57:57Z" message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.329708ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 2.105603ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 2.01182ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 2.524235ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 2.146755ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 2.10138ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:57Z" - latency: 2.148079ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:57Z" - latency: 2.365293ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:57Z" - latency: 2.152011ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:57Z" - latency: 2.140196ms message: 'network-check-target-ip-10-0-135-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-network-check-target-ip-10-0-143-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63373" uid: f9efb6f5-e235-4525-bbcd-f638c8a424a3 spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:57:57Z" message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.455284ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 1.255675ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 772.845µs message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 911.928µs message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 929.16µs message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 1.196766ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:57Z" - latency: 1.01558ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:57Z" - latency: 860.205µs message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:57Z" - latency: 881.81µs message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:57Z" - latency: 1.038959ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:50:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-108.ec2.internal uid: 12189066-db33-4e8f-9b37-d861b73b4cc0 resourceVersion: "63376" uid: c7c48d92-69f5-4155-b11f-7c885feeaed3 spec: sourcePod: network-check-source-7bc5b6bf85-lbmgq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T01:56:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.778µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:32:57Z" - latency: 1.655688ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:32:57Z" - latency: 853.322µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:31:57Z" - latency: 1.793177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:31:57Z" - latency: 836.702µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:30:57Z" - latency: 1.724971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:30:57Z" - latency: 918.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:57Z" - latency: 2.083836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:29:57Z" - latency: 839.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:57Z" - latency: 1.694533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:28:57Z" kind: List metadata: resourceVersion: ""