apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "11464"
    uid: 087696c4-8316-4f1c-877e-4d42b66ada14
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "14979"
    uid: da400cb2-fc2d-4020-af55-3fc47e941324
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:24:46Z"
      message: 'load-balancer-api-external: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.504448ms
      message: 'load-balancer-api-external: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:24:46Z"
    - latency: 7.708348ms
      message: 'load-balancer-api-external: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:24:46Z"
    - latency: 5.156134ms
      message: 'load-balancer-api-external: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:23:46Z"
    - latency: 15.782134ms
      message: 'load-balancer-api-external: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:23:46Z"
    - latency: 4.583758ms
      message: 'load-balancer-api-external: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:22:46Z"
    - latency: 8.267995ms
      message: 'load-balancer-api-external: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:22:46Z"
    - latency: 4.989815ms
      message: 'load-balancer-api-external: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:21:46Z"
    - latency: 8.999879ms
      message: 'load-balancer-api-external: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:21:46Z"
    - latency: 3.572605ms
      message: 'load-balancer-api-external: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:20:46Z"
    - latency: 7.785856ms
      message: 'load-balancer-api-external: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "14978"
    uid: ef1862fd-7b60-4270-ad19-ff530f151051
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:24:46Z"
      message: 'load-balancer-api-internal: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.250919ms
      message: 'load-balancer-api-internal: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:24:46Z"
    - latency: 7.727366ms
      message: 'load-balancer-api-internal: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:24:46Z"
    - latency: 4.930077ms
      message: 'load-balancer-api-internal: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:23:46Z"
    - latency: 15.755442ms
      message: 'load-balancer-api-internal: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:23:46Z"
    - latency: 4.614319ms
      message: 'load-balancer-api-internal: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:22:46Z"
    - latency: 8.23843ms
      message: 'load-balancer-api-internal: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:22:46Z"
    - latency: 6.451139ms
      message: 'load-balancer-api-internal: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:21:46Z"
    - latency: 9.356877ms
      message: 'load-balancer-api-internal: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:21:46Z"
    - latency: 4.265443ms
      message: 'load-balancer-api-internal: tcp connection to a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:20:46Z"
    - latency: 7.742478ms
      message: 'load-balancer-api-internal: resolved host name a60e750d502a849d4b6c9fe3c06d92d4-43f495c92072a90d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-network-check-target-ip-10-0-136-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "11462"
    uid: 2407d2b5-ee81-40f7-95ed-0689ad3f6e72
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-network-check-target-ip-10-0-137-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "11463"
    uid: 46ce739b-43ec-4711-95e3-71bc94ab0f02
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-network-check-target-ip-10-0-139-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "11461"
    uid: 1c6313b6-efa2-40f3-b8c2-6570459e6190
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-58.ec2.internal
      uid: 0f9fc002-95eb-4e96-a734-ecd92c96d066
    resourceVersion: "14977"
    uid: 3858172d-a4a6-4a1a-960c-e3f0b7431895
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kj26f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:24:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.078057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:24:46Z"
    - latency: 1.566633ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:24:46Z"
    - latency: 819.477µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:23:46Z"
    - latency: 1.841691ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:23:46Z"
    - latency: 1.015347ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:22:46Z"
    - latency: 1.967741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:22:46Z"
    - latency: 848.858µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:21:46Z"
    - latency: 2.334241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:21:46Z"
    - latency: 910.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:20:46Z"
    - latency: 1.662731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:20:46Z"
kind: List
metadata:
  resourceVersion: ""