apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "55149" uid: 9a969239-facf-45b6-b548-87bfb61cbc25 spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T04:06:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.338472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 901.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 974.509µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 1.216233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 886.395µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:30:06Z" - latency: 1.086822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:29:06Z" - latency: 969.124µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:28:06Z" - latency: 842.569µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:27:06Z" - latency: 1.308112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:26:06Z" - latency: 1.061418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:25:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "56172" uid: 175a3e48-8590-4931-9898-883861a3c192 spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:05:06Z" message: 'load-balancer-api-external: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.331946ms message: 'load-balancer-api-external: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:06Z" - latency: 6.438351ms message: 'load-balancer-api-external: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:35:06Z" - latency: 5.146338ms message: 'load-balancer-api-external: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 11.273342ms message: 'load-balancer-api-external: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:34:06Z" - latency: 3.458852ms message: 'load-balancer-api-external: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 8.150377ms message: 'load-balancer-api-external: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:33:06Z" - latency: 3.648883ms message: 'load-balancer-api-external: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 7.488377ms message: 'load-balancer-api-external: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:32:06Z" - latency: 5.493976ms message: 'load-balancer-api-external: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 7.575026ms message: 'load-balancer-api-external: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:31:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "56171" uid: 8bdee963-c1f7-470d-85e7-dc4142f4f9ff spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:05:06Z" message: 'load-balancer-api-internal: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.772211ms message: 'load-balancer-api-internal: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:06Z" - latency: 6.348138ms message: 'load-balancer-api-internal: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:35:06Z" - latency: 4.199113ms message: 'load-balancer-api-internal: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 11.341698ms message: 'load-balancer-api-internal: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:34:06Z" - latency: 3.488879ms message: 'load-balancer-api-internal: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 8.074777ms message: 'load-balancer-api-internal: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:33:06Z" - latency: 3.679346ms message: 'load-balancer-api-internal: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 7.456645ms message: 'load-balancer-api-internal: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:32:06Z" - latency: 5.518155ms message: 'load-balancer-api-internal: tcp connection to a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 7.626006ms message: 'load-balancer-api-internal: resolved host name a9f25948d16c14d36a7a2288f1c71f23-6df5ae9ad5dc626a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:31:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-130-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "55146" uid: 055177ec-13ab-4a31-b355-d2ab8d412972 spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:06:06Z" message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.378592ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 1.315116ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 961.42µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 1.018966ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 797.633µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:30:06Z" - latency: 754.052µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:29:06Z" - latency: 788.968µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:28:06Z" - latency: 1.397848ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:27:06Z" - latency: 1.244169ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:26:06Z" - latency: 853.955µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:25:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-134-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "55147" uid: 9d617650-33d2-4d44-b561-5750866a5bc1 spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:06:06Z" message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.727009ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 2.072496ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 1.605951ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 1.637592ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 1.759466ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:30:06Z" - latency: 1.592727ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:29:06Z" - latency: 1.742508ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:28:06Z" - latency: 1.686943ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:27:06Z" - latency: 1.967025ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:26:06Z" - latency: 1.651663ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:25:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-143-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "55148" uid: ae0caf9a-538b-46bd-a2f7-038757b56399 spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:06:06Z" message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.388551ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 2.353989ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 2.453439ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 2.495816ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 2.301661ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:30:06Z" - latency: 2.221695ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:29:06Z" - latency: 2.219435ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:28:06Z" - latency: 2.502337ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:27:06Z" - latency: 2.47211ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:26:06Z" - latency: 2.139669ms message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:25:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T03:59:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: c406dd85-eaa7-41fe-83d0-9d8efb4b28fc resourceVersion: "56168" uid: 11af798f-923f-4960-95e6-d0c2e4f2f394 spec: sourcePod: network-check-source-989f8b8dc-9v87h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T04:05:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 842.376µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:06Z" - latency: 1.705955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:35:06Z" - latency: 1.28697ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:06Z" - latency: 1.752213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:34:06Z" - latency: 878.013µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:06Z" - latency: 2.187812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:33:06Z" - latency: 950.006µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:06Z" - latency: 2.465564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:32:06Z" - latency: 1.419944ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:06Z" - latency: 1.972789ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:31:06Z" kind: List metadata: resourceVersion: ""