apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "10765"
    uid: 03aeae26-05b9-414f-9926-1147acafda65
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "21598"
    uid: 0d9da9cf-7e16-4bab-bee0-8b14d7853f04
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:44:59Z"
      message: 'load-balancer-api-external: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.066956ms
      message: 'load-balancer-api-external: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:44:59Z"
    - latency: 10.017604ms
      message: 'load-balancer-api-external: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:44:59Z"
    - latency: 5.459597ms
      message: 'load-balancer-api-external: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:43:59Z"
    - latency: 8.474039ms
      message: 'load-balancer-api-external: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:43:59Z"
    - latency: 5.263625ms
      message: 'load-balancer-api-external: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:42:59Z"
    - latency: 12.549272ms
      message: 'load-balancer-api-external: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:42:59Z"
    - latency: 4.423126ms
      message: 'load-balancer-api-external: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:41:59Z"
    - latency: 8.966843ms
      message: 'load-balancer-api-external: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:41:59Z"
    - latency: 4.88883ms
      message: 'load-balancer-api-external: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:40:59Z"
    - latency: 14.931259ms
      message: 'load-balancer-api-external: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:40:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "21597"
    uid: 19436196-e544-4437-b3f5-ad2aea04411f
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:44:59Z"
      message: 'load-balancer-api-internal: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.022755ms
      message: 'load-balancer-api-internal: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:44:59Z"
    - latency: 10.057485ms
      message: 'load-balancer-api-internal: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:44:59Z"
    - latency: 5.431421ms
      message: 'load-balancer-api-internal: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:43:59Z"
    - latency: 8.4383ms
      message: 'load-balancer-api-internal: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:43:59Z"
    - latency: 5.094406ms
      message: 'load-balancer-api-internal: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:42:59Z"
    - latency: 12.878416ms
      message: 'load-balancer-api-internal: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:42:59Z"
    - latency: 4.5081ms
      message: 'load-balancer-api-internal: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:41:59Z"
    - latency: 8.929558ms
      message: 'load-balancer-api-internal: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:41:59Z"
    - latency: 5.919984ms
      message: 'load-balancer-api-internal: tcp connection to ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:40:59Z"
    - latency: 14.966224ms
      message: 'load-balancer-api-internal: resolved host name ad121c593c2e34c0387d5bdd2ef84530-8b88f9d9edcc4c7e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:40:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-network-check-target-ip-10-0-130-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "10770"
    uid: 3f81d346-cd0a-4128-a322-a882a4f1c060
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-network-check-target-ip-10-0-138-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "10771"
    uid: 71b22f30-7d8a-41df-b152-bbc2e4734e44
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-network-check-target-ip-10-0-141-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "10772"
    uid: bc54affa-b98a-4a4f-8e8d-a9793ef78f99
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:38:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-123-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-123.ec2.internal
      uid: a65f12b2-4a6b-4d32-8fde-f1be06b494ed
    resourceVersion: "21596"
    uid: 0d6a8b77-1a49-4818-bafe-3592e5c2151c
  spec:
    sourcePod: network-check-source-7d88cb55d8-hc4nq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:44:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085069ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:44:59Z"
    - latency: 1.834997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:44:59Z"
    - latency: 1.026855ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:43:59Z"
    - latency: 1.774147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:43:59Z"
    - latency: 1.086049ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:42:59Z"
    - latency: 2.100336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:42:59Z"
    - latency: 819.005µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:41:59Z"
    - latency: 1.698911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:41:59Z"
    - latency: 1.087872ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:40:59Z"
    - latency: 3.977033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:40:59Z"
kind: List
metadata:
  resourceVersion: ""