apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "19074" uid: a9fdedd3-f415-4a20-bcae-32015fc712c7 spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T15:24:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.197284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 1.026963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 1.013061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:36:05Z" - latency: 736.986µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:35:05Z" - latency: 998.281µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:34:05Z" - latency: 1.140475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:33:05Z" - latency: 1.354255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:32:05Z" - latency: 1.126504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:31:05Z" - latency: 943.239µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:30:05Z" - latency: 1.027436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:29:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "20436" uid: d8ccd800-ee7a-48a6-9012-cb78b837adbd spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T15:23:05Z" message: 'load-balancer-api-external: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.66368ms message: 'load-balancer-api-external: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:41:05Z" - latency: 13.370132ms message: 'load-balancer-api-external: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:41:05Z" - latency: 5.621012ms message: 'load-balancer-api-external: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:40:05Z" - latency: 8.197708ms message: 'load-balancer-api-external: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:40:05Z" - latency: 4.605143ms message: 'load-balancer-api-external: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:39:05Z" - latency: 7.6483ms message: 'load-balancer-api-external: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:39:05Z" - latency: 4.410158ms message: 'load-balancer-api-external: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 8.185109ms message: 'load-balancer-api-external: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:38:05Z" - latency: 4.229039ms message: 'load-balancer-api-external: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 8.319962ms message: 'load-balancer-api-external: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:37:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "20435" uid: 1c20c198-d30e-4732-8d79-0a54284e2ab1 spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T15:23:05Z" message: 'load-balancer-api-internal: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.343681ms message: 'load-balancer-api-internal: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:41:05Z" - latency: 13.218277ms message: 'load-balancer-api-internal: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:41:05Z" - latency: 5.629057ms message: 'load-balancer-api-internal: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:40:05Z" - latency: 8.18681ms message: 'load-balancer-api-internal: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:40:05Z" - latency: 4.593238ms message: 'load-balancer-api-internal: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:39:05Z" - latency: 7.692754ms message: 'load-balancer-api-internal: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:39:05Z" - latency: 4.45963ms message: 'load-balancer-api-internal: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 8.159099ms message: 'load-balancer-api-internal: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:38:05Z" - latency: 5.163456ms message: 'load-balancer-api-internal: tcp connection to a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 8.401508ms message: 'load-balancer-api-internal: resolved host name a8ff6c98605414310bfcf8bcba526c9f-472ddf01f284e03e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:37:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-network-check-target-ip-10-0-135-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "19073" uid: 8d41330d-ca3f-409e-aba9-0bd10b45816c spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:24:05Z" message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.226735ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 2.197056ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 2.086133ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:36:05Z" - latency: 1.560994ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:35:05Z" - latency: 2.084424ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:34:05Z" - latency: 2.093663ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:33:05Z" - latency: 2.016589ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:32:05Z" - latency: 2.053036ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:31:05Z" - latency: 2.029097ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:30:05Z" - latency: 2.060827ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:29:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-network-check-target-ip-10-0-138-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "19072" uid: cc485c78-90b6-4171-b476-7451728a41bd spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:24:05Z" message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.73471ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 1.748196ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 1.840296ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:36:05Z" - latency: 1.626504ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:35:05Z" - latency: 1.905412ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:34:05Z" - latency: 2.002041ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:33:05Z" - latency: 1.453129ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:32:05Z" - latency: 1.725303ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:31:05Z" - latency: 2.33601ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:30:05Z" - latency: 1.74798ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:29:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-network-check-target-ip-10-0-143-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "19071" uid: 21ab3087-ece8-43eb-8b15-a698a845685d spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:24:05Z" message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.796µs message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 768.83µs message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 1.114873ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:36:05Z" - latency: 747.867µs message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:35:05Z" - latency: 802.082µs message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:34:05Z" - latency: 1.327056ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:33:05Z" - latency: 1.50342ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:32:05Z" - latency: 894.25µs message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:31:05Z" - latency: 1.368623ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:30:05Z" - latency: 824.594µs message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:29:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:17:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-125.ec2.internal uid: 6a15edc7-d575-4507-9353-a9f3fb3a39a1 resourceVersion: "20434" uid: 91b41bf6-de2e-4566-be33-59a5250501c8 spec: sourcePod: network-check-source-7d88cb55d8-5tz62 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T15:23:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.339µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:41:05Z" - latency: 2.810157ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:41:05Z" - latency: 1.005242ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:40:05Z" - latency: 1.662226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:40:05Z" - latency: 1.050538ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:39:05Z" - latency: 1.547547ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:39:05Z" - latency: 935.663µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:38:05Z" - latency: 1.655751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:38:05Z" - latency: 1.288439ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:37:05Z" - latency: 1.556639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:37:05Z" kind: List metadata: resourceVersion: ""