apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63029" uid: f20e93b4-f70f-45ec-a5af-cff3b41db7b5 spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T18:16:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 1.251444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 789.361µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 813.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 833.9µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 1.173044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:46:32Z" - latency: 787.873µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:45:32Z" - latency: 998.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:44:32Z" - latency: 918.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:32Z" - latency: 1.137983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63031" uid: 95711855-a32b-4e3f-990f-6d17f73f93a7 spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T18:15:32Z" message: 'load-balancer-api-external: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.630723ms message: 'load-balancer-api-external: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 8.912649ms message: 'load-balancer-api-external: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:51:32Z" - latency: 3.48406ms message: 'load-balancer-api-external: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 8.728289ms message: 'load-balancer-api-external: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:50:32Z" - latency: 4.778455ms message: 'load-balancer-api-external: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 8.658133ms message: 'load-balancer-api-external: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:49:32Z" - latency: 4.601201ms message: 'load-balancer-api-external: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 10.908381ms message: 'load-balancer-api-external: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:48:32Z" - latency: 5.474083ms message: 'load-balancer-api-external: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 8.021831ms message: 'load-balancer-api-external: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:47:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63030" uid: 03b84aad-20fc-4582-a548-41fff62dba6d spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T18:15:32Z" message: 'load-balancer-api-internal: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.78552ms message: 'load-balancer-api-internal: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 8.864274ms message: 'load-balancer-api-internal: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:51:32Z" - latency: 3.508374ms message: 'load-balancer-api-internal: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 8.686663ms message: 'load-balancer-api-internal: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:50:32Z" - latency: 4.751862ms message: 'load-balancer-api-internal: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 8.607747ms message: 'load-balancer-api-internal: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:49:32Z" - latency: 4.640657ms message: 'load-balancer-api-internal: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 10.836062ms message: 'load-balancer-api-internal: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:48:32Z" - latency: 5.462237ms message: 'load-balancer-api-internal: tcp connection to ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 7.985071ms message: 'load-balancer-api-internal: resolved host name ad3723d8b48e744efabb06ffb823c53d-b6e869e422968b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:47:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-ip-10-0-128-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63028" uid: a01b2c9e-4275-4534-b0cb-49da046a0a11 spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:16:32Z" message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.283948ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 2.823997ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 2.343152ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 2.206149ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 2.284596ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 2.54013ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:46:32Z" - latency: 2.5716ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:45:32Z" - latency: 2.594252ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:44:32Z" - latency: 2.441751ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:32Z" - latency: 2.257092ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-ip-10-0-132-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63025" uid: f340eeda-7c8d-41b4-9239-bf08f6c07f23 spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:16:32Z" message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186268ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 1.995823ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 2.089601ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 2.351434ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 2.370105ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 1.964777ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:46:32Z" - latency: 2.138502ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:45:32Z" - latency: 2.625759ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:44:32Z" - latency: 2.273135ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:32Z" - latency: 2.277341ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-ip-10-0-143-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63026" uid: 8cb20597-509d-4f28-a525-c5b6206a30e4 spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:16:32Z" message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.024329ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 811.682µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 666.617µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 1.471312ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 1.09795ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 701.38µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:46:32Z" - latency: 825.788µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:45:32Z" - latency: 1.382262ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:44:32Z" - latency: 1.422892ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:32Z" - latency: 876.379µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:09:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.ec2.internal uid: 9a68d19e-1e19-4741-8f91-772ec82aad60 resourceVersion: "63027" uid: 797ac2ee-2bcc-46b6-8157-0053fc4c89d4 spec: sourcePod: network-check-source-7bc5b6bf85-j9z5n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T18:15:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.83µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:51:32Z" - latency: 1.824469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:51:32Z" - latency: 868.302µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:50:32Z" - latency: 1.709023ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:50:32Z" - latency: 954.843µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:49:32Z" - latency: 1.855617ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:49:32Z" - latency: 986.351µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:48:32Z" - latency: 2.006229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:48:32Z" - latency: 1.050417ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:47:32Z" - latency: 1.589894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:47:32Z" kind: List metadata: resourceVersion: ""