apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "11187"
    uid: 379ca440-321e-4cbc-92b6-50cadfbd3b6e
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "14650"
    uid: 639c746b-eeb0-475c-aa7f-9eac2949b879
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:50:22Z"
      message: 'load-balancer-api-external: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.99786ms
      message: 'load-balancer-api-external: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:50:22Z"
    - latency: 7.558631ms
      message: 'load-balancer-api-external: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:50:22Z"
    - latency: 11.334407ms
      message: 'load-balancer-api-external: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:49:22Z"
    - latency: 7.303753ms
      message: 'load-balancer-api-external: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:49:22Z"
    - latency: 4.947641ms
      message: 'load-balancer-api-external: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:48:22Z"
    - latency: 6.51517ms
      message: 'load-balancer-api-external: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:48:22Z"
    - latency: 6.131876ms
      message: 'load-balancer-api-external: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:47:22Z"
    - latency: 10.283884ms
      message: 'load-balancer-api-external: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:47:22Z"
    - latency: 5.363312ms
      message: 'load-balancer-api-external: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:46:22Z"
    - latency: 7.143487ms
      message: 'load-balancer-api-external: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:46:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "14651"
    uid: 42d8dd58-3355-408b-8a8b-91ba4f2b9a69
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:50:22Z"
      message: 'load-balancer-api-internal: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.979777ms
      message: 'load-balancer-api-internal: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:50:22Z"
    - latency: 7.714732ms
      message: 'load-balancer-api-internal: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:50:22Z"
    - latency: 5.854681ms
      message: 'load-balancer-api-internal: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:49:22Z"
    - latency: 7.372189ms
      message: 'load-balancer-api-internal: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:49:22Z"
    - latency: 5.364583ms
      message: 'load-balancer-api-internal: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:48:22Z"
    - latency: 6.427405ms
      message: 'load-balancer-api-internal: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:48:22Z"
    - latency: 5.93339ms
      message: 'load-balancer-api-internal: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:47:22Z"
    - latency: 10.320771ms
      message: 'load-balancer-api-internal: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:47:22Z"
    - latency: 5.3708ms
      message: 'load-balancer-api-internal: tcp connection to ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:46:22Z"
    - latency: 7.104817ms
      message: 'load-balancer-api-internal: resolved host name ace00001e59524e33b174a667fa221c0-617678c79a107746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:46:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-131-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "11185"
    uid: 3971c9f3-e110-445d-82fa-ef5a87e81b04
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-134-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "11184"
    uid: 04aa516a-2710-490b-8398-ef4fcd7018d2
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-140-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "11183"
    uid: f9d17768-4bb4-474e-bcb1-6bdfb4e86865
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-192-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-192.ec2.internal
      uid: 182db079-c297-42f4-a68b-977a900abe60
    resourceVersion: "14649"
    uid: 3e1b4f40-ce1a-4835-8504-da222da4057a
  spec:
    sourcePod: network-check-source-685456655f-xkvbb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:50:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.297µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:50:22Z"
    - latency: 1.804312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:50:22Z"
    - latency: 863.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:49:22Z"
    - latency: 2.213708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:49:22Z"
    - latency: 822.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:48:22Z"
    - latency: 1.876235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:48:22Z"
    - latency: 1.15596ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:47:22Z"
    - latency: 1.582407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:47:22Z"
    - latency: 855.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:46:22Z"
    - latency: 1.718201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:46:22Z"
kind: List
metadata:
  resourceVersion: ""