apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "14309"
    uid: ef6eb39f-2d46-4e45-af6c-3ace7196efa6
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.685µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:23Z"
    - latency: 1.032721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:23Z"
    - latency: 1.181626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:23Z"
    - latency: 950.247µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:23Z"
    - latency: 929.943µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:23Z"
    - latency: 1.057473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:23Z"
    - latency: 1.053421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "16050"
    uid: d2da440c-69f1-483a-8026-badb6f19c7e3
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:23Z"
      message: 'load-balancer-api-external: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.568208ms
      message: 'load-balancer-api-external: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:06:23Z"
    - latency: 8.14728ms
      message: 'load-balancer-api-external: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:06:23Z"
    - latency: 5.446705ms
      message: 'load-balancer-api-external: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:23Z"
    - latency: 9.087281ms
      message: 'load-balancer-api-external: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:23Z"
    - latency: 4.584476ms
      message: 'load-balancer-api-external: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:23Z"
    - latency: 8.195252ms
      message: 'load-balancer-api-external: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:23Z"
    - latency: 5.623447ms
      message: 'load-balancer-api-external: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:23Z"
    - latency: 8.436417ms
      message: 'load-balancer-api-external: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:23Z"
    - latency: 5.949595ms
      message: 'load-balancer-api-external: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:23Z"
    - latency: 8.507034ms
      message: 'load-balancer-api-external: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "16049"
    uid: d99279cf-2dae-4e72-a328-6268602feab2
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:23Z"
      message: 'load-balancer-api-internal: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.513259ms
      message: 'load-balancer-api-internal: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:06:23Z"
    - latency: 8.217617ms
      message: 'load-balancer-api-internal: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:06:23Z"
    - latency: 5.468806ms
      message: 'load-balancer-api-internal: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:23Z"
    - latency: 9.017666ms
      message: 'load-balancer-api-internal: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:23Z"
    - latency: 4.557191ms
      message: 'load-balancer-api-internal: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:23Z"
    - latency: 8.272371ms
      message: 'load-balancer-api-internal: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:23Z"
    - latency: 4.640712ms
      message: 'load-balancer-api-internal: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:23Z"
    - latency: 8.401115ms
      message: 'load-balancer-api-internal: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:23Z"
    - latency: 5.949006ms
      message: 'load-balancer-api-internal: tcp connection to ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:23Z"
    - latency: 8.549101ms
      message: 'load-balancer-api-internal: resolved host name ab51cd70f875d4b419bbf203ae35c218-dd2c9e2ca6cc1df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-network-check-target-ip-10-0-132-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "14308"
    uid: d853106b-6f6b-493c-9c0c-f5168ee93c26
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:23Z"
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.32263ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:23Z"
    - latency: 2.728018ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:23Z"
    - latency: 2.39129ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:23Z"
    - latency: 2.397397ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:23Z"
    - latency: 2.210238ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:23Z"
    - latency: 2.264077ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:23Z"
    - latency: 2.574202ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-network-check-target-ip-10-0-140-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "14307"
    uid: eab96db9-24e2-4462-b676-8df6d8bc58fc
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:23Z"
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16553ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:23Z"
    - latency: 2.736045ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:23Z"
    - latency: 2.185986ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:23Z"
    - latency: 2.240677ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:23Z"
    - latency: 2.620362ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:23Z"
    - latency: 2.494799ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:23Z"
    - latency: 2.330496ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-network-check-target-ip-10-0-140-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "14306"
    uid: dbaa990e-56ad-47f2-baec-9661199d2ec0
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:23Z"
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.065µs
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:23Z"
    - latency: 1.564906ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:23Z"
    - latency: 933.964µs
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:23Z"
    - latency: 946.26µs
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:23Z"
    - latency: 1.074159ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:23Z"
    - latency: 782.357µs
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:23Z"
    - latency: 1.235121ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-8.ec2.internal
      uid: 05425802-6629-41b2-be1c-ecc304b9e281
    resourceVersion: "16047"
    uid: cdbd723a-1bff-4f45-a869-e1536a9caefa
  spec:
    sourcePod: network-check-source-7d88cb55d8-6dpqb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.409437ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:06:23Z"
    - latency: 1.70126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:06:23Z"
    - latency: 977.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:23Z"
    - latency: 2.634214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:23Z"
    - latency: 822.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:23Z"
    - latency: 1.643637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:23Z"
    - latency: 813.643µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:23Z"
    - latency: 1.708194ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:23Z"
    - latency: 866.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:23Z"
    - latency: 1.629561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:23Z"
kind: List
metadata:
  resourceVersion: ""