apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "10672"
    uid: 4b0dae46-07c8-448b-8ceb-a0fbec850fda
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "13981"
    uid: 1fd46445-8aaa-4e87-955a-ab47ee1d6e3c
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T07:49:57Z"
      message: 'load-balancer-api-external: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.889777ms
      message: 'load-balancer-api-external: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:49:57Z"
    - latency: 6.655803ms
      message: 'load-balancer-api-external: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:49:57Z"
    - latency: 4.835117ms
      message: 'load-balancer-api-external: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:48:57Z"
    - latency: 8.945792ms
      message: 'load-balancer-api-external: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:48:57Z"
    - latency: 4.414676ms
      message: 'load-balancer-api-external: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:47:57Z"
    - latency: 7.704501ms
      message: 'load-balancer-api-external: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:47:57Z"
    - latency: 5.275629ms
      message: 'load-balancer-api-external: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:46:57Z"
    - latency: 7.141452ms
      message: 'load-balancer-api-external: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:46:57Z"
    - latency: 4.569135ms
      message: 'load-balancer-api-external: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:45:57Z"
    - latency: 6.352693ms
      message: 'load-balancer-api-external: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:45:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "13982"
    uid: c0fcb5d8-051a-4c34-817c-1d75f62a42c5
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T07:49:57Z"
      message: 'load-balancer-api-internal: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.907597ms
      message: 'load-balancer-api-internal: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:49:57Z"
    - latency: 6.690103ms
      message: 'load-balancer-api-internal: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:49:57Z"
    - latency: 4.871935ms
      message: 'load-balancer-api-internal: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:48:57Z"
    - latency: 8.972953ms
      message: 'load-balancer-api-internal: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:48:57Z"
    - latency: 5.440203ms
      message: 'load-balancer-api-internal: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:47:57Z"
    - latency: 7.764446ms
      message: 'load-balancer-api-internal: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:47:57Z"
    - latency: 5.316181ms
      message: 'load-balancer-api-internal: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:46:57Z"
    - latency: 7.119626ms
      message: 'load-balancer-api-internal: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:46:57Z"
    - latency: 4.491258ms
      message: 'load-balancer-api-internal: tcp connection to a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:45:57Z"
    - latency: 6.385257ms
      message: 'load-balancer-api-internal: resolved host name a4dda8dfbf14544f1922a8ac2d2508d4-5beb60fd4e37e99f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:45:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-network-check-target-ip-10-0-130-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "10670"
    uid: d419900a-b058-47e0-9e83-1cbb9d93f860
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-network-check-target-ip-10-0-141-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "10668"
    uid: 1281c5ac-940f-4007-bac3-2aabc8c47c59
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-network-check-target-ip-10-0-142-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "10669"
    uid: 7a8112d4-1aea-400d-b4e4-6aaee38ae2c8
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T07:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-27-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-27.ec2.internal
      uid: 55d8b55e-23a6-42cb-bc89-99076f91d3c1
    resourceVersion: "13980"
    uid: 99f3215d-8ad4-4c0e-b7a3-b3b02c42ff23
  spec:
    sourcePod: network-check-source-6f8b768455-wlblw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T07:49:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.265µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:49:57Z"
    - latency: 1.7015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:49:57Z"
    - latency: 1.205453ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:48:57Z"
    - latency: 1.653493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:48:57Z"
    - latency: 962.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:47:57Z"
    - latency: 1.62454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:47:57Z"
    - latency: 828.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:46:57Z"
    - latency: 1.650709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:46:57Z"
    - latency: 1.040667ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T07:45:57Z"
    - latency: 1.529822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T07:45:57Z"
kind: List
metadata:
  resourceVersion: ""