apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "10764"
    uid: e255f96f-9005-4a07-9451-be50805cd4f0
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "14408"
    uid: aa9f4bbb-7a89-41eb-90c1-56fd7697027a
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:04:21Z"
      message: 'load-balancer-api-external: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.580844ms
      message: 'load-balancer-api-external: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:04:21Z"
    - latency: 10.050094ms
      message: 'load-balancer-api-external: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:04:21Z"
    - latency: 4.586295ms
      message: 'load-balancer-api-external: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:21Z"
    - latency: 7.581948ms
      message: 'load-balancer-api-external: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:03:21Z"
    - latency: 4.410533ms
      message: 'load-balancer-api-external: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:21Z"
    - latency: 6.792812ms
      message: 'load-balancer-api-external: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:02:21Z"
    - latency: 4.588917ms
      message: 'load-balancer-api-external: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:21Z"
    - latency: 7.081394ms
      message: 'load-balancer-api-external: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:01:21Z"
    - latency: 3.864136ms
      message: 'load-balancer-api-external: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:21Z"
    - latency: 6.513931ms
      message: 'load-balancer-api-external: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:00:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "14409"
    uid: c7474d94-d2f4-413f-b034-7c433ad257ee
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:04:21Z"
      message: 'load-balancer-api-internal: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.677707ms
      message: 'load-balancer-api-internal: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:04:21Z"
    - latency: 10.240221ms
      message: 'load-balancer-api-internal: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:04:21Z"
    - latency: 4.480189ms
      message: 'load-balancer-api-internal: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:21Z"
    - latency: 7.528478ms
      message: 'load-balancer-api-internal: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:03:21Z"
    - latency: 3.918919ms
      message: 'load-balancer-api-internal: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:21Z"
    - latency: 6.746742ms
      message: 'load-balancer-api-internal: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:02:21Z"
    - latency: 4.580437ms
      message: 'load-balancer-api-internal: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:21Z"
    - latency: 7.181549ms
      message: 'load-balancer-api-internal: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:01:21Z"
    - latency: 3.888089ms
      message: 'load-balancer-api-internal: tcp connection to a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:21Z"
    - latency: 6.608551ms
      message: 'load-balancer-api-internal: resolved host name a2095454e593f490793c01a3772bc85a-9e2001c27bcf8180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:00:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-network-check-target-ip-10-0-131-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "10769"
    uid: c77e3857-2139-4627-a376-a443c0fad533
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-network-check-target-ip-10-0-139-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "10771"
    uid: f360abdc-9ad8-4055-8375-f7e63f0d95ca
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-network-check-target-ip-10-0-142-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "10770"
    uid: ed61eefa-9324-4969-8095-18d2f475177e
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:58:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-86-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-86.ec2.internal
      uid: 04f528e6-ed4b-4ade-a6cc-f4487ff54f1f
    resourceVersion: "14407"
    uid: f64886b4-08ef-4ac2-82ff-9384a04467e3
  spec:
    sourcePod: network-check-source-685456655f-v6l6x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:04:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.564µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:04:21Z"
    - latency: 2.256261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:04:21Z"
    - latency: 821.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:21Z"
    - latency: 1.949055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:03:21Z"
    - latency: 878.737µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:21Z"
    - latency: 1.955171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:02:21Z"
    - latency: 913.431µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:21Z"
    - latency: 2.110578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:01:21Z"
    - latency: 1.105795ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:21Z"
    - latency: 1.638792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:00:21Z"
kind: List
metadata:
  resourceVersion: ""