apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "10960"
    uid: 62613901-846f-4cd9-8d67-19702068140b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "14535"
    uid: 9eab63fa-8415-472d-9bdd-6ebb7495e730
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T08:26:21Z"
      message: 'load-balancer-api-external: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.702594ms
      message: 'load-balancer-api-external: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:26:21Z"
    - latency: 6.365665ms
      message: 'load-balancer-api-external: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:26:21Z"
    - latency: 4.815876ms
      message: 'load-balancer-api-external: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:25:21Z"
    - latency: 9.084746ms
      message: 'load-balancer-api-external: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:25:21Z"
    - latency: 4.489234ms
      message: 'load-balancer-api-external: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:24:21Z"
    - latency: 6.083895ms
      message: 'load-balancer-api-external: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:24:21Z"
    - latency: 5.066089ms
      message: 'load-balancer-api-external: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:23:21Z"
    - latency: 7.339518ms
      message: 'load-balancer-api-external: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:23:21Z"
    - latency: 5.849538ms
      message: 'load-balancer-api-external: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:22:21Z"
    - latency: 10.15155ms
      message: 'load-balancer-api-external: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:22:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "14536"
    uid: bd762308-5118-4dff-9be5-03809195adba
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T08:26:21Z"
      message: 'load-balancer-api-internal: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.328384ms
      message: 'load-balancer-api-internal: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:26:21Z"
    - latency: 6.366191ms
      message: 'load-balancer-api-internal: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:26:21Z"
    - latency: 5.288202ms
      message: 'load-balancer-api-internal: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:25:21Z"
    - latency: 9.055818ms
      message: 'load-balancer-api-internal: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:25:21Z"
    - latency: 5.2438ms
      message: 'load-balancer-api-internal: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:24:21Z"
    - latency: 6.041921ms
      message: 'load-balancer-api-internal: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:24:21Z"
    - latency: 5.275945ms
      message: 'load-balancer-api-internal: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:23:21Z"
    - latency: 7.317023ms
      message: 'load-balancer-api-internal: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:23:21Z"
    - latency: 5.856175ms
      message: 'load-balancer-api-internal: tcp connection to a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:22:21Z"
    - latency: 10.126363ms
      message: 'load-balancer-api-internal: resolved host name a8b0d8b2908fc4ed0a8381e366d5344e-8569d397115acff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:22:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-network-check-target-ip-10-0-139-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "10959"
    uid: cec5f063-0039-4a02-8b35-186de3074f83
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-network-check-target-ip-10-0-141-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "10958"
    uid: c8cb9cdb-9bc4-44fa-bcd6-75c97173723b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-network-check-target-ip-10-0-143-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "10956"
    uid: e53ebcbb-3655-41f2-9868-e4eea6320ef8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T08:20:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-233-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-233.ec2.internal
      uid: 6b75944c-5d09-4d63-a604-68675151609d
    resourceVersion: "14534"
    uid: 91f8763b-9358-475b-a73b-854169b4b374
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fmmbx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T08:26:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:26:21Z"
    - latency: 1.700597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:26:21Z"
    - latency: 959.517µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:25:21Z"
    - latency: 1.972504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:25:21Z"
    - latency: 928.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:24:21Z"
    - latency: 1.660082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:24:21Z"
    - latency: 1.189346ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:23:21Z"
    - latency: 1.490477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:23:21Z"
    - latency: 782.356µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T08:22:21Z"
    - latency: 5.742294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T08:22:21Z"
kind: List
metadata:
  resourceVersion: ""