apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "73201" uid: f1da4f79-357c-41cc-acf1-bd6673287089 spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T17:44:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.209791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:33:16Z" - latency: 1.604699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:32:16Z" - latency: 1.187428ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 847.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 1.064844ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 929.532µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 1.087541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 1.621737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:26:16Z" - latency: 1.094622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:25:16Z" - latency: 1.065987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "71401" uid: de19280b-2ff3-4075-8662-07e4cdedc29f spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:43:16Z" message: 'load-balancer-api-external: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.385365ms message: 'load-balancer-api-external: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 6.825678ms message: 'load-balancer-api-external: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:31:16Z" - latency: 5.505906ms message: 'load-balancer-api-external: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 6.595618ms message: 'load-balancer-api-external: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:30:16Z" - latency: 3.658483ms message: 'load-balancer-api-external: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 6.668073ms message: 'load-balancer-api-external: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:29:16Z" - latency: 4.579263ms message: 'load-balancer-api-external: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 7.2917ms message: 'load-balancer-api-external: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:28:16Z" - latency: 4.856216ms message: 'load-balancer-api-external: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 6.809545ms message: 'load-balancer-api-external: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:27:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "71400" uid: 57a27d0b-b19a-4e37-af06-b2468a5e4682 spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:43:16Z" message: 'load-balancer-api-internal: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.335263ms message: 'load-balancer-api-internal: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 6.899596ms message: 'load-balancer-api-internal: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:31:16Z" - latency: 5.521255ms message: 'load-balancer-api-internal: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 6.549441ms message: 'load-balancer-api-internal: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:30:16Z" - latency: 11.307083ms message: 'load-balancer-api-internal: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 6.754136ms message: 'load-balancer-api-internal: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:29:16Z" - latency: 4.568502ms message: 'load-balancer-api-internal: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 7.251448ms message: 'load-balancer-api-internal: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:28:16Z" - latency: 4.88226ms message: 'load-balancer-api-internal: tcp connection to a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 6.89717ms message: 'load-balancer-api-internal: resolved host name a234ef8dfd07f471f93f2e4c9057ec6a-4c12daa1fb24f147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:27:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-network-check-target-ip-10-0-129-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "73200" uid: f5ac64d1-06c7-4785-9f0b-667b1091fe88 spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:44:16Z" message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.184357ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:33:16Z" - latency: 2.414856ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:32:16Z" - latency: 2.409445ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 2.31451ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 1.950076ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 2.07883ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 2.240199ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 2.091592ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:26:16Z" - latency: 2.169804ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:25:16Z" - latency: 2.20913ms message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-network-check-target-ip-10-0-131-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "73198" uid: 50dbf66a-a424-411d-b6ba-5d7a6b1a1f58 spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:44:16Z" message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.803932ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:33:16Z" - latency: 2.424048ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:32:16Z" - latency: 1.947522ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 1.748169ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 1.734317ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 1.741463ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 1.879872ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 1.844947ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:26:16Z" - latency: 1.971959ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:25:16Z" - latency: 2.049936ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-network-check-target-ip-10-0-143-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "73199" uid: 135e1585-602b-4701-be83-927eb379a283 spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:44:16Z" message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.124443ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:33:16Z" - latency: 1.091051ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:32:16Z" - latency: 1.236161ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 1.002987ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 785.574µs message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 1.379071ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 1.21591ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 912.747µs message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:26:16Z" - latency: 1.380662ms message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:25:16Z" - latency: 699.856µs message: 'network-check-target-ip-10-0-143-87: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:37:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-87-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-87.ec2.internal uid: 87a0db21-2d61-4467-b12f-8ee816e7a9a1 resourceVersion: "71399" uid: aaad5db8-da3c-43e9-8ef9-dd6c982cc844 spec: sourcePod: network-check-source-65bdbbff45-sxq82 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T17:43:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 805.191µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:31:16Z" - latency: 1.761794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:31:16Z" - latency: 818.593µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:30:16Z" - latency: 1.805377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:30:16Z" - latency: 1.164786ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:29:16Z" - latency: 1.644624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:29:16Z" - latency: 821.361µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:28:16Z" - latency: 1.846892ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:28:16Z" - latency: 743.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:27:16Z" - latency: 1.846071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:27:16Z" kind: List metadata: resourceVersion: ""