apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "11919"
    uid: eaf2f158-1fcf-4405-be39-2f66241fcf38
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "14689"
    uid: 86ba639e-46c1-4008-9126-43be20ee6b97
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:53:40Z"
      message: 'load-balancer-api-external: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.829379ms
      message: 'load-balancer-api-external: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:53:40Z"
    - latency: 8.978988ms
      message: 'load-balancer-api-external: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:53:40Z"
    - latency: 5.489439ms
      message: 'load-balancer-api-external: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:52:40Z"
    - latency: 8.442655ms
      message: 'load-balancer-api-external: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:52:40Z"
    - latency: 4.927378ms
      message: 'load-balancer-api-external: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:51:40Z"
    - latency: 8.272078ms
      message: 'load-balancer-api-external: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:51:40Z"
    - latency: 3.526102ms
      message: 'load-balancer-api-external: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:50:40Z"
    - latency: 9.636788ms
      message: 'load-balancer-api-external: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:50:40Z"
    - latency: 4.608498ms
      message: 'load-balancer-api-external: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:49:40Z"
    - latency: 8.361844ms
      message: 'load-balancer-api-external: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:49:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "14690"
    uid: 7f60c1e7-a4a1-4940-af5d-6e5cfd8140a7
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:53:40Z"
      message: 'load-balancer-api-internal: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.833896ms
      message: 'load-balancer-api-internal: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:53:40Z"
    - latency: 8.930174ms
      message: 'load-balancer-api-internal: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:53:40Z"
    - latency: 5.49618ms
      message: 'load-balancer-api-internal: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:52:40Z"
    - latency: 8.377473ms
      message: 'load-balancer-api-internal: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:52:40Z"
    - latency: 4.929998ms
      message: 'load-balancer-api-internal: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:51:40Z"
    - latency: 8.211402ms
      message: 'load-balancer-api-internal: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:51:40Z"
    - latency: 4.468609ms
      message: 'load-balancer-api-internal: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:50:40Z"
    - latency: 9.707439ms
      message: 'load-balancer-api-internal: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:50:40Z"
    - latency: 3.606151ms
      message: 'load-balancer-api-internal: tcp connection to ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:49:40Z"
    - latency: 8.315353ms
      message: 'load-balancer-api-internal: resolved host name ae673ebd1d2d94a77979cf1bf4f044d4-66d4575ed5e01ae7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:49:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-network-check-target-ip-10-0-129-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "12173"
    uid: 59f883d4-b9bb-4c92-8cae-546fe02fb52b
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-network-check-target-ip-10-0-137-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "11924"
    uid: ab5d8268-3a59-46dd-9e73-f8cffaac8ad1
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-network-check-target-ip-10-0-143-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "11925"
    uid: 7f443493-283a-40a4-97c4-37b306d8a23f
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-144.ec2.internal
      uid: 28001f6d-876d-4b5a-a655-edf3d1397369
    resourceVersion: "14688"
    uid: a7b868e7-9036-4ed0-b01d-91c25bd5e248
  spec:
    sourcePod: network-check-source-8894fc9bd-z62vj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:53:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 705.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:53:40Z"
    - latency: 2.759018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:53:40Z"
    - latency: 873.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:52:40Z"
    - latency: 1.775188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:52:40Z"
    - latency: 850.217µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:51:40Z"
    - latency: 1.781732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:51:40Z"
    - latency: 801.167µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:50:40Z"
    - latency: 1.575149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:50:40Z"
    - latency: 843.976µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T16:49:40Z"
    - latency: 1.746077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T16:49:40Z"
kind: List
metadata:
  resourceVersion: ""