apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "11245"
    uid: a7b3aefb-af82-4c62-8fdd-ea60a6110303
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "14656"
    uid: efc4f3d7-85b1-423b-b61e-aed7946b5e2b
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:49:47Z"
      message: 'load-balancer-api-external: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.808836ms
      message: 'load-balancer-api-external: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:49:47Z"
    - latency: 7.160123ms
      message: 'load-balancer-api-external: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:49:47Z"
    - latency: 8.243548ms
      message: 'load-balancer-api-external: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:48:47Z"
    - latency: 8.551806ms
      message: 'load-balancer-api-external: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:48:47Z"
    - latency: 5.337395ms
      message: 'load-balancer-api-external: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:47:47Z"
    - latency: 9.198401ms
      message: 'load-balancer-api-external: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:47:47Z"
    - latency: 5.300375ms
      message: 'load-balancer-api-external: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:46:47Z"
    - latency: 8.773277ms
      message: 'load-balancer-api-external: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:46:47Z"
    - latency: 3.83403ms
      message: 'load-balancer-api-external: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:45:47Z"
    - latency: 8.213095ms
      message: 'load-balancer-api-external: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:45:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "14657"
    uid: e21e933a-c093-43ca-bb84-ca1fb1c6e450
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:49:47Z"
      message: 'load-balancer-api-internal: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.995557ms
      message: 'load-balancer-api-internal: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:49:47Z"
    - latency: 6.970577ms
      message: 'load-balancer-api-internal: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:49:47Z"
    - latency: 7.696716ms
      message: 'load-balancer-api-internal: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:48:47Z"
    - latency: 8.466715ms
      message: 'load-balancer-api-internal: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:48:47Z"
    - latency: 5.334245ms
      message: 'load-balancer-api-internal: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:47:47Z"
    - latency: 9.020369ms
      message: 'load-balancer-api-internal: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:47:47Z"
    - latency: 5.360082ms
      message: 'load-balancer-api-internal: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:46:47Z"
    - latency: 8.639782ms
      message: 'load-balancer-api-internal: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:46:47Z"
    - latency: 4.78794ms
      message: 'load-balancer-api-internal: tcp connection to a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:45:47Z"
    - latency: 8.093284ms
      message: 'load-balancer-api-internal: resolved host name a45556c5fd7c84043a6a163f60585d8f-376861328335f454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:45:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-136-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "11253"
    uid: 7d643516-3cee-45ad-972d-de9f2d738151
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-138-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "11252"
    uid: c05f0efe-3869-4062-a18b-d2db83a08422
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-141-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "11250"
    uid: 861fb166-0ecc-42e8-9f08-38dcfb04a7bb
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:43:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-124-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-124.ec2.internal
      uid: 1bfed7e4-b38e-4fe3-9b5b-a3805dd558e4
    resourceVersion: "14655"
    uid: 4a00a6ad-853e-44d0-b5fd-b742314bfc72
  spec:
    sourcePod: network-check-source-685456655f-w6twf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:49:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 793.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:49:47Z"
    - latency: 1.716677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:49:47Z"
    - latency: 986.328µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:48:47Z"
    - latency: 1.961571ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:48:47Z"
    - latency: 922.968µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:47:47Z"
    - latency: 2.477164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:47:47Z"
    - latency: 1.041879ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:46:47Z"
    - latency: 1.946606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:46:47Z"
    - latency: 951.212µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:45:47Z"
    - latency: 2.201217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:45:47Z"
kind: List
metadata:
  resourceVersion: ""