apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "11163"
    uid: 6f391563-d055-40f6-869d-e68bbbac9a09
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "13503"
    uid: c0802024-e8fc-4ecb-bfd3-def6650e7479
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:12:11Z"
      message: 'load-balancer-api-external: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.186678ms
      message: 'load-balancer-api-external: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:12:11Z"
    - latency: 8.00696ms
      message: 'load-balancer-api-external: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:12:11Z"
    - latency: 3.702068ms
      message: 'load-balancer-api-external: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:11:11Z"
    - latency: 7.920606ms
      message: 'load-balancer-api-external: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:11:11Z"
    - latency: 4.988695ms
      message: 'load-balancer-api-external: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:10:11Z"
    - latency: 8.587193ms
      message: 'load-balancer-api-external: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:10:11Z"
    - latency: 5.666812ms
      message: 'load-balancer-api-external: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:09:11Z"
    - latency: 7.630234ms
      message: 'load-balancer-api-external: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:09:11Z"
    - latency: 5.409133ms
      message: 'load-balancer-api-external: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:08:11Z"
    - latency: 7.884261ms
      message: 'load-balancer-api-external: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:08:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "13504"
    uid: 1b354e4f-fc36-45e4-a2d8-4a95a631b53f
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:12:11Z"
      message: 'load-balancer-api-internal: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.299165ms
      message: 'load-balancer-api-internal: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:12:11Z"
    - latency: 8.041484ms
      message: 'load-balancer-api-internal: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:12:11Z"
    - latency: 4.736403ms
      message: 'load-balancer-api-internal: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:11:11Z"
    - latency: 7.958847ms
      message: 'load-balancer-api-internal: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:11:11Z"
    - latency: 3.765445ms
      message: 'load-balancer-api-internal: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:10:11Z"
    - latency: 8.69612ms
      message: 'load-balancer-api-internal: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:10:11Z"
    - latency: 5.603828ms
      message: 'load-balancer-api-internal: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:09:11Z"
    - latency: 7.657918ms
      message: 'load-balancer-api-internal: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:09:11Z"
    - latency: 5.371495ms
      message: 'load-balancer-api-internal: tcp connection to af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:08:11Z"
    - latency: 7.910404ms
      message: 'load-balancer-api-internal: resolved host name af0c2a5efe0e94ea1a169f12072d64e3-72ef3e0d572f6e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:08:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-network-check-target-ip-10-0-130-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "11169"
    uid: e8116680-c8dc-404d-949e-4b855fa6c58b
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-network-check-target-ip-10-0-136-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "11170"
    uid: b2032550-0fe5-4e10-911d-54ec143c97e4
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-network-check-target-ip-10-0-141-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "11168"
    uid: f4ae302d-0953-48c1-87c2-b7621faeaef5
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-245-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-245.ec2.internal
      uid: af7375fb-2f66-4781-8ec7-0cb554e94cac
    resourceVersion: "13502"
    uid: 1bc1e3f5-61c4-426a-b389-e261f9cf574b
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ld7d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:12:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:12:11Z"
    - latency: 1.666671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:12:11Z"
    - latency: 831.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:11:11Z"
    - latency: 1.635984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:11:11Z"
    - latency: 804.053µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:10:11Z"
    - latency: 1.641394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:10:11Z"
    - latency: 764.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:09:11Z"
    - latency: 1.501187ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:09:11Z"
    - latency: 1.024761ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:08:11Z"
    - latency: 1.662796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:08:11Z"
kind: List
metadata:
  resourceVersion: ""