apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "10585"
    uid: 309aa260-ea9a-482b-9578-341f01616a6f
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "19890"
    uid: d0c4bd3a-edbf-4897-b102-3fed95ab3c96
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:51:28Z"
      message: 'load-balancer-api-external: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.405335ms
      message: 'load-balancer-api-external: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:28Z"
    - latency: 6.429988ms
      message: 'load-balancer-api-external: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:51:28Z"
    - latency: 3.992144ms
      message: 'load-balancer-api-external: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:50:28Z"
    - latency: 6.781508ms
      message: 'load-balancer-api-external: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:50:28Z"
    - latency: 10.840279ms
      message: 'load-balancer-api-external: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:49:28Z"
    - latency: 6.922252ms
      message: 'load-balancer-api-external: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:49:28Z"
    - latency: 4.485656ms
      message: 'load-balancer-api-external: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:48:28Z"
    - latency: 8.898271ms
      message: 'load-balancer-api-external: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:48:28Z"
    - latency: 8.392615ms
      message: 'load-balancer-api-external: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:47:28Z"
    - latency: 6.534852ms
      message: 'load-balancer-api-external: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:47:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "19891"
    uid: 25796577-657c-42d0-a826-dacdd99c325a
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:51:28Z"
      message: 'load-balancer-api-internal: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.007514ms
      message: 'load-balancer-api-internal: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:28Z"
    - latency: 6.378356ms
      message: 'load-balancer-api-internal: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:51:28Z"
    - latency: 4.017887ms
      message: 'load-balancer-api-internal: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:50:28Z"
    - latency: 6.745825ms
      message: 'load-balancer-api-internal: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:50:28Z"
    - latency: 6.0567ms
      message: 'load-balancer-api-internal: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:49:28Z"
    - latency: 7.565194ms
      message: 'load-balancer-api-internal: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:49:28Z"
    - latency: 6.688113ms
      message: 'load-balancer-api-internal: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:48:28Z"
    - latency: 9.112555ms
      message: 'load-balancer-api-internal: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:48:28Z"
    - latency: 7.24629ms
      message: 'load-balancer-api-internal: tcp connection to a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:47:28Z"
    - latency: 6.684187ms
      message: 'load-balancer-api-internal: resolved host name a39663ffba32e4dacb7c8146daecccfb-500f0429c431e107.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:47:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-network-check-target-ip-10-0-140-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "10592"
    uid: a9374a06-62ea-4a11-88d7-bea95edcd2cb
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-network-check-target-ip-10-0-140-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "10590"
    uid: d4931aef-6716-4f8e-8e1b-b3b842be1029
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-network-check-target-ip-10-0-142-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "10591"
    uid: 2749becf-b941-499a-a084-51d94e1c6fd1
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:45:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-151.ec2.internal
      uid: 4ddff70e-315c-47f3-b3c4-2d805c540b98
    resourceVersion: "19889"
    uid: 06e9e13d-ebf2-4880-857f-ddd7d5af308b
  spec:
    sourcePod: network-check-source-685456655f-jvgps
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:51:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:28Z"
    - latency: 1.927027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:51:28Z"
    - latency: 1.174468ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:50:28Z"
    - latency: 2.075055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:50:28Z"
    - latency: 822.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:49:28Z"
    - latency: 2.023149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:49:28Z"
    - latency: 1.049712ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:48:28Z"
    - latency: 1.761495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:48:28Z"
    - latency: 812.471µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:47:28Z"
    - latency: 2.114303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:47:28Z"
kind: List
metadata:
  resourceVersion: ""