apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "15021"
    uid: 029722db-535a-44fb-8e53-540f3a6ee46d
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:00:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:36Z"
    - latency: 1.471868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 813.539µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 1.039246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 1.124939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 904.849µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 1.223979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "14448"
    uid: 92729fa4-2dfe-45d3-90f5-db84e44c9277
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:59:36Z"
      message: 'load-balancer-api-external: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.629232ms
      message: 'load-balancer-api-external: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 7.658939ms
      message: 'load-balancer-api-external: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 5.693466ms
      message: 'load-balancer-api-external: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 7.191049ms
      message: 'load-balancer-api-external: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 5.340253ms
      message: 'load-balancer-api-external: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 10.294875ms
      message: 'load-balancer-api-external: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 5.425635ms
      message: 'load-balancer-api-external: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 6.298945ms
      message: 'load-balancer-api-external: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 4.468424ms
      message: 'load-balancer-api-external: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 7.144172ms
      message: 'load-balancer-api-external: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "14449"
    uid: 418c597e-6fe0-4091-b2f7-93458eb2a5e8
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:59:36Z"
      message: 'load-balancer-api-internal: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.633704ms
      message: 'load-balancer-api-internal: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 7.631429ms
      message: 'load-balancer-api-internal: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 5.663324ms
      message: 'load-balancer-api-internal: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 7.25577ms
      message: 'load-balancer-api-internal: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 5.327677ms
      message: 'load-balancer-api-internal: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 10.359929ms
      message: 'load-balancer-api-internal: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 5.337661ms
      message: 'load-balancer-api-internal: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 6.329909ms
      message: 'load-balancer-api-internal: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 4.47686ms
      message: 'load-balancer-api-internal: tcp connection to a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 7.109811ms
      message: 'load-balancer-api-internal: resolved host name a4741d98994cf4033991d6fe1708d484-2d2a74d3b3026dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-network-check-target-ip-10-0-130-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "15018"
    uid: 03152506-a12c-47e3-8b70-9a2096dddff2
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:00:36Z"
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.432493ms
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:36Z"
    - latency: 942.765µs
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 986.412µs
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 1.783316ms
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 846µs
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 902.911µs
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 1.195472ms
      message: 'network-check-target-ip-10-0-130-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-network-check-target-ip-10-0-140-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "15019"
    uid: 3cd22c0f-c1ab-40e8-bdcd-89ad7bfbd89c
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:00:36Z"
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.521042ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:36Z"
    - latency: 2.587734ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 2.704525ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 2.594012ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 2.32443ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 2.268037ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 2.600098ms
      message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-network-check-target-ip-10-0-142-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "15020"
    uid: f5844164-0b44-42c9-a24e-6c561160831c
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:00:36Z"
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401653ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:36Z"
    - latency: 2.559767ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 2.694504ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 2.708662ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 2.143026ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 2.307722ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 2.857151ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:53:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-45.ec2.internal
      uid: c05d5a9e-fcce-494a-84ae-81e7b5ef3349
    resourceVersion: "14447"
    uid: b951fdc2-d751-4014-b843-a7550d9a10f8
  spec:
    sourcePod: network-check-source-989f8b8dc-9nmxm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:59:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 1.793341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:59:36Z"
    - latency: 791.901µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 2.595269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:36Z"
    - latency: 1.653278ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 2.056866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:36Z"
    - latency: 796.205µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 1.722956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:36Z"
    - latency: 905.706µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:36Z"
    - latency: 1.741183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:36Z"
kind: List
metadata:
  resourceVersion: ""