apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "11074"
    uid: 2e0c0688-3663-4b57-88a9-d23a343dc049
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "14836"
    uid: d7071dcb-038c-4e64-804d-4bcd97bdd581
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:46:22Z"
      message: 'load-balancer-api-external: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.066124ms
      message: 'load-balancer-api-external: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:22Z"
    - latency: 6.253987ms
      message: 'load-balancer-api-external: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:46:22Z"
    - latency: 6.090468ms
      message: 'load-balancer-api-external: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:22Z"
    - latency: 8.333377ms
      message: 'load-balancer-api-external: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:45:22Z"
    - latency: 4.520903ms
      message: 'load-balancer-api-external: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:44:22Z"
    - latency: 7.719034ms
      message: 'load-balancer-api-external: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:44:22Z"
    - latency: 4.958765ms
      message: 'load-balancer-api-external: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:43:22Z"
    - latency: 7.78501ms
      message: 'load-balancer-api-external: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:43:22Z"
    - latency: 4.72423ms
      message: 'load-balancer-api-external: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:42:22Z"
    - latency: 11.004218ms
      message: 'load-balancer-api-external: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:42:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "14835"
    uid: c0201105-1f29-47ef-a257-ba1b2ab9805b
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:46:22Z"
      message: 'load-balancer-api-internal: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.124647ms
      message: 'load-balancer-api-internal: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:22Z"
    - latency: 6.203602ms
      message: 'load-balancer-api-internal: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:46:22Z"
    - latency: 5.245527ms
      message: 'load-balancer-api-internal: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:22Z"
    - latency: 8.442403ms
      message: 'load-balancer-api-internal: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:45:22Z"
    - latency: 4.514266ms
      message: 'load-balancer-api-internal: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:44:22Z"
    - latency: 7.642081ms
      message: 'load-balancer-api-internal: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:44:22Z"
    - latency: 4.964749ms
      message: 'load-balancer-api-internal: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:43:22Z"
    - latency: 7.861211ms
      message: 'load-balancer-api-internal: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:43:22Z"
    - latency: 4.596387ms
      message: 'load-balancer-api-internal: tcp connection to af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:42:22Z"
    - latency: 11.130457ms
      message: 'load-balancer-api-internal: resolved host name af99a425568ab45639e415acd522e058-621591ac5885e120.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:42:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-network-check-target-ip-10-0-137-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "11073"
    uid: 2680c503-c3f2-4638-b3ce-5f21344c74ce
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-network-check-target-ip-10-0-138-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "11072"
    uid: 22a36a10-d264-4188-843e-bdd9fb08e5a2
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-network-check-target-ip-10-0-140-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "11070"
    uid: 8d448f66-530d-4740-a78b-bcdf0a4e1a93
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:40:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-48.ec2.internal
      uid: 24b0d130-ac9a-4bf6-9426-46f69faa5ff4
    resourceVersion: "14834"
    uid: c6f8605c-f4d1-412e-904d-d7d904f135a3
  spec:
    sourcePod: network-check-source-7d88cb55d8-2d9kd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:46:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.3745ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:22Z"
    - latency: 1.529812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:46:22Z"
    - latency: 824.635µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:22Z"
    - latency: 1.61918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:45:22Z"
    - latency: 821.167µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:44:22Z"
    - latency: 1.458817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:44:22Z"
    - latency: 827.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:43:22Z"
    - latency: 1.437634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:43:22Z"
    - latency: 1.837213ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:42:22Z"
    - latency: 2.018009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:42:22Z"
kind: List
metadata:
  resourceVersion: ""