apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "11028"
    uid: 4b653414-59a3-4b4d-8ad4-2f81552de669
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "14822"
    uid: bfb46a53-39cd-491b-ba2c-167f62dae7e4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T14:19:27Z"
      message: 'load-balancer-api-external: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.131569ms
      message: 'load-balancer-api-external: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:19:27Z"
    - latency: 7.12106ms
      message: 'load-balancer-api-external: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:19:27Z"
    - latency: 3.861204ms
      message: 'load-balancer-api-external: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:18:27Z"
    - latency: 8.635007ms
      message: 'load-balancer-api-external: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:18:27Z"
    - latency: 5.320039ms
      message: 'load-balancer-api-external: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:17:27Z"
    - latency: 11.279324ms
      message: 'load-balancer-api-external: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:17:27Z"
    - latency: 4.29721ms
      message: 'load-balancer-api-external: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:16:27Z"
    - latency: 7.973194ms
      message: 'load-balancer-api-external: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:16:27Z"
    - latency: 4.107652ms
      message: 'load-balancer-api-external: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:15:27Z"
    - latency: 7.120869ms
      message: 'load-balancer-api-external: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:15:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "14823"
    uid: 952615c2-f8f1-4310-960a-7540d768f92b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T14:19:27Z"
      message: 'load-balancer-api-internal: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.076381ms
      message: 'load-balancer-api-internal: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:19:27Z"
    - latency: 7.176459ms
      message: 'load-balancer-api-internal: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:19:27Z"
    - latency: 5.048385ms
      message: 'load-balancer-api-internal: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:18:27Z"
    - latency: 8.567385ms
      message: 'load-balancer-api-internal: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:18:27Z"
    - latency: 5.207303ms
      message: 'load-balancer-api-internal: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:17:27Z"
    - latency: 11.324245ms
      message: 'load-balancer-api-internal: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:17:27Z"
    - latency: 5.752327ms
      message: 'load-balancer-api-internal: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:16:27Z"
    - latency: 7.957345ms
      message: 'load-balancer-api-internal: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:16:27Z"
    - latency: 5.259853ms
      message: 'load-balancer-api-internal: tcp connection to ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:15:27Z"
    - latency: 7.134885ms
      message: 'load-balancer-api-internal: resolved host name ac3a697770ef2442aacfe2886ab161f6-33509663a35ff431.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:15:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-ip-10-0-138-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "11033"
    uid: 88c1e3a1-0393-4e48-9b04-3df8cfd719bc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-ip-10-0-140-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "11035"
    uid: cbe46277-4734-4a3e-a37d-897df3d80a58
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-ip-10-0-141-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "11034"
    uid: 2a869d3f-dd38-4c70-b344-7301d3adefe8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: 44a20c88-1c7e-4138-907f-cba847690a9c
    resourceVersion: "14821"
    uid: 61c93816-53d6-4c8b-8f2c-bf41cbeb9d69
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjlpb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T14:19:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 941.694µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:19:27Z"
    - latency: 1.804313ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:19:27Z"
    - latency: 802.814µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:18:27Z"
    - latency: 1.843738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:18:27Z"
    - latency: 1.058128ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:17:27Z"
    - latency: 1.889067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:17:27Z"
    - latency: 868.595µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:16:27Z"
    - latency: 2.005438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:16:27Z"
    - latency: 1.034634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:15:27Z"
    - latency: 2.084753ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:15:27Z"
kind: List
metadata:
  resourceVersion: ""