apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "10834"
    uid: e196aab0-69a0-479e-bae0-f172a546ae2b
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "14116"
    uid: b9679d22-b02f-42b5-bd85-038178ffeec5
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:00:34Z"
      message: 'load-balancer-api-external: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.826506ms
      message: 'load-balancer-api-external: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:34Z"
    - latency: 6.207877ms
      message: 'load-balancer-api-external: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:00:34Z"
    - latency: 4.145058ms
      message: 'load-balancer-api-external: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:34Z"
    - latency: 6.705053ms
      message: 'load-balancer-api-external: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:59:34Z"
    - latency: 4.49287ms
      message: 'load-balancer-api-external: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:34Z"
    - latency: 7.13745ms
      message: 'load-balancer-api-external: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:58:34Z"
    - latency: 4.310832ms
      message: 'load-balancer-api-external: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:34Z"
    - latency: 17.110938ms
      message: 'load-balancer-api-external: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:57:34Z"
    - latency: 4.874165ms
      message: 'load-balancer-api-external: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:56:34Z"
    - latency: 8.350196ms
      message: 'load-balancer-api-external: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "14115"
    uid: 8ef01dcd-84c4-4a92-8b92-b15fac677ef8
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:00:34Z"
      message: 'load-balancer-api-internal: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.477292ms
      message: 'load-balancer-api-internal: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:34Z"
    - latency: 6.289984ms
      message: 'load-balancer-api-internal: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:00:34Z"
    - latency: 4.281114ms
      message: 'load-balancer-api-internal: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:34Z"
    - latency: 6.653171ms
      message: 'load-balancer-api-internal: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:59:34Z"
    - latency: 4.449879ms
      message: 'load-balancer-api-internal: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:34Z"
    - latency: 7.25045ms
      message: 'load-balancer-api-internal: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:58:34Z"
    - latency: 4.890209ms
      message: 'load-balancer-api-internal: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:34Z"
    - latency: 17.156754ms
      message: 'load-balancer-api-internal: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:57:34Z"
    - latency: 4.137817ms
      message: 'load-balancer-api-internal: tcp connection to a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:56:34Z"
    - latency: 8.41983ms
      message: 'load-balancer-api-internal: resolved host name a24fadb388de9417f95ff561898ae1bc-b40b50b1bdede33b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-network-check-target-ip-10-0-132-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "10832"
    uid: b15e4e3a-f403-4c66-84e6-ea6ed05ef11d
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-network-check-target-ip-10-0-133-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "10833"
    uid: 70069b36-df58-44c1-9d55-79748eb19fe4
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-network-check-target-ip-10-0-138-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "10831"
    uid: 79407140-9169-49f4-b273-19d090341832
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:54:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-222.ec2.internal
      uid: 7f245042-162a-44c0-8a56-7d9765a4d65d
    resourceVersion: "14114"
    uid: d173fc84-1ebd-4d18-89ec-cfa63585c08e
  spec:
    sourcePod: network-check-source-685456655f-qlbtw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:00:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044562ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:34Z"
    - latency: 1.853952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:00:34Z"
    - latency: 779.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:34Z"
    - latency: 1.599402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:59:34Z"
    - latency: 824.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:34Z"
    - latency: 2.018429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:58:34Z"
    - latency: 742.793µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:34Z"
    - latency: 12.233189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:57:34Z"
    - latency: 1.055653ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:56:34Z"
    - latency: 1.682936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:56:34Z"
kind: List
metadata:
  resourceVersion: ""