apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "10898"
    uid: 10648bdd-ad5e-4371-be4e-aab3473d8ed3
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "14433"
    uid: 7bede335-4ea9-436a-b1b2-1ddc3cde73cb
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T09:40:51Z"
      message: 'load-balancer-api-external: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.862341ms
      message: 'load-balancer-api-external: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:40:51Z"
    - latency: 8.466624ms
      message: 'load-balancer-api-external: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:40:51Z"
    - latency: 5.171037ms
      message: 'load-balancer-api-external: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:39:51Z"
    - latency: 8.960491ms
      message: 'load-balancer-api-external: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:39:51Z"
    - latency: 4.645665ms
      message: 'load-balancer-api-external: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:38:51Z"
    - latency: 8.22048ms
      message: 'load-balancer-api-external: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:38:51Z"
    - latency: 4.017987ms
      message: 'load-balancer-api-external: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:37:51Z"
    - latency: 13.32823ms
      message: 'load-balancer-api-external: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:37:51Z"
    - latency: 4.007269ms
      message: 'load-balancer-api-external: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:36:51Z"
    - latency: 7.732573ms
      message: 'load-balancer-api-external: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:36:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "14434"
    uid: c5781d9a-5c40-4bce-8bf5-1f93b367a2da
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T09:40:51Z"
      message: 'load-balancer-api-internal: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.847795ms
      message: 'load-balancer-api-internal: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:40:51Z"
    - latency: 7.625505ms
      message: 'load-balancer-api-internal: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:40:51Z"
    - latency: 5.260312ms
      message: 'load-balancer-api-internal: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:39:51Z"
    - latency: 8.846435ms
      message: 'load-balancer-api-internal: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:39:51Z"
    - latency: 4.670772ms
      message: 'load-balancer-api-internal: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:38:51Z"
    - latency: 8.093284ms
      message: 'load-balancer-api-internal: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:38:51Z"
    - latency: 4.025802ms
      message: 'load-balancer-api-internal: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:37:51Z"
    - latency: 13.267637ms
      message: 'load-balancer-api-internal: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:37:51Z"
    - latency: 4.494674ms
      message: 'load-balancer-api-internal: tcp connection to ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:36:51Z"
    - latency: 7.642144ms
      message: 'load-balancer-api-internal: resolved host name ac1473f09c17946bba6bc22a6e070231-a21eef09feaf0f2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:36:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-network-check-target-ip-10-0-128-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "10903"
    uid: bc698c17-2784-4a46-92ac-c223df0a4ca2
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-network-check-target-ip-10-0-133-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "10904"
    uid: dae738c0-e8a2-4532-991b-c3871efd651a
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-network-check-target-ip-10-0-134-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "10905"
    uid: 815952f4-e736-4212-94bb-2838ad4d8078
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:34:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-14-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-14.ec2.internal
      uid: bfdcf3bc-1532-409c-886f-fab673595477
    resourceVersion: "14432"
    uid: d5798f41-f03b-4751-8d09-072ef23237bc
  spec:
    sourcePod: network-check-source-65bdbbff45-hxmbq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T09:40:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 723.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:40:51Z"
    - latency: 1.816216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:40:51Z"
    - latency: 1.110336ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:39:51Z"
    - latency: 1.644849ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:39:51Z"
    - latency: 774.242µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:38:51Z"
    - latency: 1.633114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:38:51Z"
    - latency: 895.117µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:37:51Z"
    - latency: 5.470466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:37:51Z"
    - latency: 787.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T09:36:51Z"
    - latency: 1.584328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T09:36:51Z"
kind: List
metadata:
  resourceVersion: ""