apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "10812"
    uid: 8ea21e77-609d-42e1-86a3-afb0f993f8fe
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "21147"
    uid: 0afd6b35-51b5-481c-83cf-fdc793516597
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:41:26Z"
      message: 'load-balancer-api-external: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.031818ms
      message: 'load-balancer-api-external: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:26Z"
    - latency: 7.54467ms
      message: 'load-balancer-api-external: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:41:26Z"
    - latency: 4.863658ms
      message: 'load-balancer-api-external: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:26Z"
    - latency: 6.581929ms
      message: 'load-balancer-api-external: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:40:26Z"
    - latency: 6.61092ms
      message: 'load-balancer-api-external: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:26Z"
    - latency: 7.397293ms
      message: 'load-balancer-api-external: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:39:26Z"
    - latency: 4.739705ms
      message: 'load-balancer-api-external: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:26Z"
    - latency: 9.259666ms
      message: 'load-balancer-api-external: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:38:26Z"
    - latency: 4.117982ms
      message: 'load-balancer-api-external: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:26Z"
    - latency: 6.466062ms
      message: 'load-balancer-api-external: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "21148"
    uid: ff8fb703-ddec-40ce-ad81-78d983d546bb
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:41:26Z"
      message: 'load-balancer-api-internal: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.881015ms
      message: 'load-balancer-api-internal: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:26Z"
    - latency: 7.439241ms
      message: 'load-balancer-api-internal: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:41:26Z"
    - latency: 4.513884ms
      message: 'load-balancer-api-internal: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:26Z"
    - latency: 6.505477ms
      message: 'load-balancer-api-internal: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:40:26Z"
    - latency: 6.703325ms
      message: 'load-balancer-api-internal: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:26Z"
    - latency: 7.472648ms
      message: 'load-balancer-api-internal: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:39:26Z"
    - latency: 4.770363ms
      message: 'load-balancer-api-internal: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:26Z"
    - latency: 9.070962ms
      message: 'load-balancer-api-internal: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:38:26Z"
    - latency: 5.970109ms
      message: 'load-balancer-api-internal: tcp connection to a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:26Z"
    - latency: 6.323884ms
      message: 'load-balancer-api-internal: resolved host name a27d3974c953241e38640034dbb1f131-92dc8ae245a9add6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-network-check-target-ip-10-0-132-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "10808"
    uid: 058bc1c2-400e-491c-a45c-c77f7218db54
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-network-check-target-ip-10-0-136-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "10810"
    uid: 91459d54-3032-4452-a346-5ca4382bc8c5
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-network-check-target-ip-10-0-140-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "10811"
    uid: cce1fe03-e141-44bb-8d4e-be0fa0da83f2
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-220-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-220.ec2.internal
      uid: 148414f3-a100-40ca-a636-0f03b23a8f01
    resourceVersion: "21146"
    uid: d89db44d-35fe-4e6f-8f82-1bc7a1aa15c6
  spec:
    sourcePod: network-check-source-869dcfcdcd-4gcz4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:41:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.752345ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:26Z"
    - latency: 2.10388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:41:26Z"
    - latency: 868.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:26Z"
    - latency: 1.722684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:40:26Z"
    - latency: 1.054999ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:26Z"
    - latency: 1.765973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:39:26Z"
    - latency: 1.138081ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:26Z"
    - latency: 1.604675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:38:26Z"
    - latency: 1.021371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:26Z"
    - latency: 1.787838ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:37:26Z"
kind: List
metadata:
  resourceVersion: ""