apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "10692"
    uid: 9320c2c7-e1db-4805-b349-551f464eaffd
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "14096"
    uid: 4c6f78f6-4029-498f-919c-977c7cc72e3a
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:19Z"
      message: 'load-balancer-api-external: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.764238ms
      message: 'load-balancer-api-external: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:16:19Z"
    - latency: 7.655653ms
      message: 'load-balancer-api-external: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:16:19Z"
    - latency: 5.864584ms
      message: 'load-balancer-api-external: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:15:19Z"
    - latency: 6.4003ms
      message: 'load-balancer-api-external: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:15:19Z"
    - latency: 5.477949ms
      message: 'load-balancer-api-external: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:14:19Z"
    - latency: 8.971206ms
      message: 'load-balancer-api-external: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:14:19Z"
    - latency: 5.787374ms
      message: 'load-balancer-api-external: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:13:19Z"
    - latency: 6.955446ms
      message: 'load-balancer-api-external: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:13:19Z"
    - latency: 4.720015ms
      message: 'load-balancer-api-external: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:12:19Z"
    - latency: 7.141706ms
      message: 'load-balancer-api-external: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:12:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "14095"
    uid: bc3c0265-8496-4fda-b4b3-a7256be40917
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:19Z"
      message: 'load-balancer-api-internal: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.79968ms
      message: 'load-balancer-api-internal: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:16:19Z"
    - latency: 7.721238ms
      message: 'load-balancer-api-internal: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:16:19Z"
    - latency: 5.261854ms
      message: 'load-balancer-api-internal: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:15:19Z"
    - latency: 6.410729ms
      message: 'load-balancer-api-internal: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:15:19Z"
    - latency: 5.473435ms
      message: 'load-balancer-api-internal: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:14:19Z"
    - latency: 9.00245ms
      message: 'load-balancer-api-internal: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:14:19Z"
    - latency: 5.78084ms
      message: 'load-balancer-api-internal: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:13:19Z"
    - latency: 7.010879ms
      message: 'load-balancer-api-internal: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:13:19Z"
    - latency: 4.708833ms
      message: 'load-balancer-api-internal: tcp connection to aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:12:19Z"
    - latency: 7.058864ms
      message: 'load-balancer-api-internal: resolved host name aa9498219b4a14518abf2270c4c77e74-99e9ad3879a8e738.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:12:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-129-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "10701"
    uid: 81f70ea4-5d1f-44c2-b3fb-a4987bc495ee
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-130-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "10699"
    uid: 5d99d0d0-1eaf-4e1f-aa5b-c2c87da2f775
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-131-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "10703"
    uid: 5b475d5e-0f75-452b-a059-4db2940b9a4a
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:10:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 8e2973b1-5e11-448a-b5af-1151353dc690
    resourceVersion: "14094"
    uid: e4a9f80e-8aa8-4c54-8de7-0f494a6e276e
  spec:
    sourcePod: network-check-source-6f8b768455-nh59f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.126679ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:16:19Z"
    - latency: 1.909152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:16:19Z"
    - latency: 980.333µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:15:19Z"
    - latency: 1.952125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:15:19Z"
    - latency: 904.203µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:14:19Z"
    - latency: 2.115586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:14:19Z"
    - latency: 1.144563ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:13:19Z"
    - latency: 1.816101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:13:19Z"
    - latency: 831.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:12:19Z"
    - latency: 1.847849ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:12:19Z"
kind: List
metadata:
  resourceVersion: ""