apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "23085"
    uid: 3d117879-dfe6-4b0d-af3b-459e4b5eb616
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:21:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.202µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:21:10Z"
    - latency: 1.454741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:20:10Z"
    - latency: 1.384441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:19:10Z"
    - latency: 932.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:18:10Z"
    - latency: 1.287407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:17:10Z"
    - latency: 1.307402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:16:10Z"
    - latency: 919.742µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:15:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "27173"
    uid: e0ea6620-22e5-44d0-947b-e9e93aa58ed7
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:20:10Z"
      message: 'load-balancer-api-external: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.166956ms
      message: 'load-balancer-api-external: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:26:10Z"
    - latency: 9.613107ms
      message: 'load-balancer-api-external: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:26:10Z"
    - latency: 3.920004ms
      message: 'load-balancer-api-external: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:25:10Z"
    - latency: 9.105098ms
      message: 'load-balancer-api-external: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:25:10Z"
    - latency: 5.287968ms
      message: 'load-balancer-api-external: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:24:10Z"
    - latency: 7.54238ms
      message: 'load-balancer-api-external: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:24:10Z"
    - latency: 5.211595ms
      message: 'load-balancer-api-external: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:23:10Z"
    - latency: 15.426913ms
      message: 'load-balancer-api-external: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:23:10Z"
    - latency: 4.914907ms
      message: 'load-balancer-api-external: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:22:10Z"
    - latency: 8.586058ms
      message: 'load-balancer-api-external: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "27174"
    uid: 5eab9e6d-db31-4913-930a-0ec7430f659e
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:20:10Z"
      message: 'load-balancer-api-internal: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.292261ms
      message: 'load-balancer-api-internal: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:26:10Z"
    - latency: 9.525284ms
      message: 'load-balancer-api-internal: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:26:10Z"
    - latency: 3.960336ms
      message: 'load-balancer-api-internal: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:25:10Z"
    - latency: 9.085209ms
      message: 'load-balancer-api-internal: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:25:10Z"
    - latency: 5.287351ms
      message: 'load-balancer-api-internal: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:24:10Z"
    - latency: 7.505452ms
      message: 'load-balancer-api-internal: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:24:10Z"
    - latency: 5.257437ms
      message: 'load-balancer-api-internal: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:23:10Z"
    - latency: 15.398283ms
      message: 'load-balancer-api-internal: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:23:10Z"
    - latency: 4.961155ms
      message: 'load-balancer-api-internal: tcp connection to a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:22:10Z"
    - latency: 8.550091ms
      message: 'load-balancer-api-internal: resolved host name a8cf0ee1ef0fe4ca8b386b73eb116bab-8d6391a11f83a365.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-137-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "23082"
    uid: 82650acd-7c85-4157-956f-956c14329e37
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:21:10Z"
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.365605ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:21:10Z"
    - latency: 2.679417ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:20:10Z"
    - latency: 2.664837ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:19:10Z"
    - latency: 2.178876ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:18:10Z"
    - latency: 2.33273ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:17:10Z"
    - latency: 2.490198ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:16:10Z"
    - latency: 2.635989ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:15:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-140-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "23083"
    uid: f8700032-10cb-4012-a962-750a0e6820cf
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:21:10Z"
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330877ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:21:10Z"
    - latency: 2.475488ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:20:10Z"
    - latency: 2.391914ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:19:10Z"
    - latency: 2.569935ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:18:10Z"
    - latency: 2.34497ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:17:10Z"
    - latency: 2.952593ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:16:10Z"
    - latency: 2.618077ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:15:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-143-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "23081"
    uid: 0e7eb098-a3ed-4ecc-b636-f6f69f460b83
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:21:10Z"
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032674ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:21:10Z"
    - latency: 909.857µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:20:10Z"
    - latency: 1.557696ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:19:10Z"
    - latency: 1.562902ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:18:10Z"
    - latency: 1.594553ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:17:10Z"
    - latency: 1.230038ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:16:10Z"
    - latency: 1.763803ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:15:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:14:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 88517bb4-83a7-499c-b548-9bb307e51e49
    resourceVersion: "27172"
    uid: 9e1524ee-5eb1-49cd-8ff2-7a77c3e44075
  spec:
    sourcePod: network-check-source-869dcfcdcd-ww4cz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:20:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.444µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:26:10Z"
    - latency: 2.289248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:26:10Z"
    - latency: 999.799µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:25:10Z"
    - latency: 1.893646ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:25:10Z"
    - latency: 959.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:24:10Z"
    - latency: 1.62899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:24:10Z"
    - latency: 789.783µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:23:10Z"
    - latency: 2.205694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:23:10Z"
    - latency: 1.43876ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:22:10Z"
    - latency: 1.692481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T15:22:10Z"
kind: List
metadata:
  resourceVersion: ""