apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "11313"
    uid: 294d58c0-f8b3-4772-b72c-7f190bb69460
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "14789"
    uid: 86721f23-726f-4676-8c00-74c27e9c69bb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T09:04:30Z"
      message: 'load-balancer-api-external: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.586727ms
      message: 'load-balancer-api-external: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:30Z"
    - latency: 7.708289ms
      message: 'load-balancer-api-external: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:04:30Z"
    - latency: 6.174857ms
      message: 'load-balancer-api-external: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:30Z"
    - latency: 7.763742ms
      message: 'load-balancer-api-external: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:03:30Z"
    - latency: 5.544003ms
      message: 'load-balancer-api-external: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:30Z"
    - latency: 7.098902ms
      message: 'load-balancer-api-external: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:02:30Z"
    - latency: 4.977309ms
      message: 'load-balancer-api-external: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:30Z"
    - latency: 7.197902ms
      message: 'load-balancer-api-external: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:01:30Z"
    - latency: 8.058966ms
      message: 'load-balancer-api-external: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:30Z"
    - latency: 6.25795ms
      message: 'load-balancer-api-external: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:00:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "14790"
    uid: 3ad51a12-04a4-4df8-be7f-6213d9db3934
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T09:04:30Z"
      message: 'load-balancer-api-internal: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.589791ms
      message: 'load-balancer-api-internal: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:30Z"
    - latency: 7.75393ms
      message: 'load-balancer-api-internal: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:04:30Z"
    - latency: 6.23133ms
      message: 'load-balancer-api-internal: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:30Z"
    - latency: 7.749743ms
      message: 'load-balancer-api-internal: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:03:30Z"
    - latency: 5.486555ms
      message: 'load-balancer-api-internal: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:30Z"
    - latency: 7.197445ms
      message: 'load-balancer-api-internal: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:02:30Z"
    - latency: 5.583201ms
      message: 'load-balancer-api-internal: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:30Z"
    - latency: 7.252388ms
      message: 'load-balancer-api-internal: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:01:30Z"
    - latency: 5.456246ms
      message: 'load-balancer-api-internal: tcp connection to a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:30Z"
    - latency: 6.370596ms
      message: 'load-balancer-api-internal: resolved host name a9a2ee809a6d04ebab4cef89c2e1283f-8c0c388ba5c4e2af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:00:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-network-check-target-ip-10-0-128-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "11311"
    uid: fd7be8a1-1716-426e-8cc4-8a120d886c0b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-network-check-target-ip-10-0-132-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "11310"
    uid: e7476b25-b75f-45e6-9d28-0e021b8e2712
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-network-check-target-ip-10-0-141-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "11309"
    uid: b17cd402-1c6a-428b-85f5-c9fc4dd36548
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-18-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-18.ec2.internal
      uid: 1473bc88-ef54-41c9-973f-cd6d0447dc0c
    resourceVersion: "14788"
    uid: 7d6c7aea-395e-4751-8684-3dbc81123ee2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vt9m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T09:04:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.008305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:30Z"
    - latency: 1.792897ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:04:30Z"
    - latency: 1.112932ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:30Z"
    - latency: 1.934974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:03:30Z"
    - latency: 899.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:30Z"
    - latency: 1.937624ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:02:30Z"
    - latency: 1.183103ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:30Z"
    - latency: 1.787348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:01:30Z"
    - latency: 879.196µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:30Z"
    - latency: 1.790799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:00:30Z"
kind: List
metadata:
  resourceVersion: ""