apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "10696"
    uid: a36b5ff7-5dce-4038-8c7f-6ce28200c7b9
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "14065"
    uid: ef62507b-579d-45be-8318-56851e78021c
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:16:00Z"
      message: 'load-balancer-api-external: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810853ms
      message: 'load-balancer-api-external: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:16:00Z"
    - latency: 6.382595ms
      message: 'load-balancer-api-external: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:16:00Z"
    - latency: 3.278899ms
      message: 'load-balancer-api-external: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:15:00Z"
    - latency: 6.735804ms
      message: 'load-balancer-api-external: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:15:00Z"
    - latency: 6.682448ms
      message: 'load-balancer-api-external: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:14:00Z"
    - latency: 6.18837ms
      message: 'load-balancer-api-external: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:14:00Z"
    - latency: 6.823616ms
      message: 'load-balancer-api-external: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:13:00Z"
    - latency: 7.024853ms
      message: 'load-balancer-api-external: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:13:00Z"
    - latency: 18.533403ms
      message: 'load-balancer-api-external: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:12:00Z"
    - latency: 11.103488ms
      message: 'load-balancer-api-external: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "14064"
    uid: fbd9a5a0-ad1e-4f78-8174-bbb37fe61dfc
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:16:00Z"
      message: 'load-balancer-api-internal: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.796013ms
      message: 'load-balancer-api-internal: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:16:00Z"
    - latency: 6.406438ms
      message: 'load-balancer-api-internal: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:16:00Z"
    - latency: 3.344529ms
      message: 'load-balancer-api-internal: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:15:00Z"
    - latency: 6.686002ms
      message: 'load-balancer-api-internal: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:15:00Z"
    - latency: 6.717783ms
      message: 'load-balancer-api-internal: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:14:00Z"
    - latency: 6.079367ms
      message: 'load-balancer-api-internal: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:14:00Z"
    - latency: 6.823914ms
      message: 'load-balancer-api-internal: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:13:00Z"
    - latency: 6.958523ms
      message: 'load-balancer-api-internal: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:13:00Z"
    - latency: 7.62444ms
      message: 'load-balancer-api-internal: tcp connection to a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:12:00Z"
    - latency: 11.130768ms
      message: 'load-balancer-api-internal: resolved host name a93eaa6110bf74e0ea46e71e5312aceb-43fb6cee17fdcc14.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-130-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "10702"
    uid: 098ed182-5a3c-43fe-a2db-1eb6bdfd3036
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-133-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "10700"
    uid: 33fb1a2f-6a9e-4d8f-be06-fce9f1c975b3
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-138-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "10703"
    uid: 8dca38d7-0724-4228-9daf-e3bae9541887
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: 6a8e24aa-d164-45ef-9bdb-2d8c5de7a305
    resourceVersion: "14063"
    uid: f46ceb16-e607-4e3e-acc1-a7e7c8464f9a
  spec:
    sourcePod: network-check-source-56d84b9f44-rzrvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:16:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.108µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:16:00Z"
    - latency: 1.758026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:16:00Z"
    - latency: 848.386µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:15:00Z"
    - latency: 1.778396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:15:00Z"
    - latency: 910.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:14:00Z"
    - latency: 1.933807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:14:00Z"
    - latency: 849.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:13:00Z"
    - latency: 1.995669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:13:00Z"
    - latency: 1.594272ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:12:00Z"
    - latency: 1.917093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:12:00Z"
kind: List
metadata:
  resourceVersion: ""