apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "10851"
    uid: 764bb8a5-2c90-4bd1-8ab7-2d1a98f6d426
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "21524"
    uid: ae985d1f-c16a-4ea8-8e66-f7aa38034b46
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:26:08Z"
      message: 'load-balancer-api-external: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.871412ms
      message: 'load-balancer-api-external: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:26:08Z"
    - latency: 8.88408ms
      message: 'load-balancer-api-external: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:26:08Z"
    - latency: 5.764034ms
      message: 'load-balancer-api-external: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:25:08Z"
    - latency: 10.824927ms
      message: 'load-balancer-api-external: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:25:08Z"
    - latency: 4.560481ms
      message: 'load-balancer-api-external: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:24:08Z"
    - latency: 9.716899ms
      message: 'load-balancer-api-external: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:24:08Z"
    - latency: 4.5381ms
      message: 'load-balancer-api-external: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:23:08Z"
    - latency: 23.454172ms
      message: 'load-balancer-api-external: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:23:08Z"
    - latency: 4.414233ms
      message: 'load-balancer-api-external: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:22:08Z"
    - latency: 9.995969ms
      message: 'load-balancer-api-external: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:22:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "21525"
    uid: d0eb6a21-9629-4d31-8972-276cfaa220b5
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:26:08Z"
      message: 'load-balancer-api-internal: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.883127ms
      message: 'load-balancer-api-internal: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:26:08Z"
    - latency: 8.808298ms
      message: 'load-balancer-api-internal: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:26:08Z"
    - latency: 4.301077ms
      message: 'load-balancer-api-internal: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:25:08Z"
    - latency: 10.769858ms
      message: 'load-balancer-api-internal: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:25:08Z"
    - latency: 4.610177ms
      message: 'load-balancer-api-internal: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:24:08Z"
    - latency: 9.746195ms
      message: 'load-balancer-api-internal: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:24:08Z"
    - latency: 6.983976ms
      message: 'load-balancer-api-internal: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:23:08Z"
    - latency: 23.540065ms
      message: 'load-balancer-api-internal: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:23:08Z"
    - latency: 4.401311ms
      message: 'load-balancer-api-internal: tcp connection to ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:22:08Z"
    - latency: 10.110351ms
      message: 'load-balancer-api-internal: resolved host name ac59c4998ced74ff596b50913d1fde14-377e230b372e5852.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:22:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-network-check-target-ip-10-0-130-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "10857"
    uid: ffba5361-3ee8-4cc8-86a1-8ca908fd9bee
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-network-check-target-ip-10-0-130-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "10858"
    uid: db633651-a987-4399-a3b6-6b8a5388f9bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-network-check-target-ip-10-0-139-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "10856"
    uid: f9e073c6-25be-484d-855e-ed99d30b06db
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:20:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-109-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-109.ec2.internal
      uid: cc6e009a-7690-477a-81bb-372360f7dfe7
    resourceVersion: "21523"
    uid: 8870713b-7e67-4e60-b05d-f58307823572
  spec:
    sourcePod: network-check-source-7d88cb55d8-w6gwd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:26:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.412957ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:26:08Z"
    - latency: 1.889988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:26:08Z"
    - latency: 1.004423ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:25:08Z"
    - latency: 2.777108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:25:08Z"
    - latency: 1.03643ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:24:08Z"
    - latency: 2.48126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:24:08Z"
    - latency: 829.491µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:23:08Z"
    - latency: 16.489189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:23:08Z"
    - latency: 1.33556ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:22:08Z"
    - latency: 2.098183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:22:08Z"
kind: List
metadata:
  resourceVersion: ""