apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "15299"
    uid: f3a63397-68a3-401e-8b31-5316a25ba312
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.545508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:20Z"
    - latency: 966.8µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 1.405509ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 916.852µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 975.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 5.233976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 839.811µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "14797"
    uid: b98ec0d4-0303-40e5-97dd-c1d1568063da
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:51:20Z"
      message: 'load-balancer-api-external: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.955865ms
      message: 'load-balancer-api-external: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 6.637624ms
      message: 'load-balancer-api-external: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 5.747354ms
      message: 'load-balancer-api-external: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 6.58267ms
      message: 'load-balancer-api-external: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 4.66448ms
      message: 'load-balancer-api-external: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 6.908344ms
      message: 'load-balancer-api-external: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 3.664659ms
      message: 'load-balancer-api-external: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 6.431651ms
      message: 'load-balancer-api-external: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 5.665397ms
      message: 'load-balancer-api-external: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 9.542355ms
      message: 'load-balancer-api-external: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:47:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "14796"
    uid: c8a3a75c-d16b-49d1-90d1-2944d39d3ff7
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:51:20Z"
      message: 'load-balancer-api-internal: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.539515ms
      message: 'load-balancer-api-internal: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 6.732235ms
      message: 'load-balancer-api-internal: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 5.191977ms
      message: 'load-balancer-api-internal: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 6.673141ms
      message: 'load-balancer-api-internal: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 4.693581ms
      message: 'load-balancer-api-internal: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 6.871467ms
      message: 'load-balancer-api-internal: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 4.168866ms
      message: 'load-balancer-api-internal: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 6.465691ms
      message: 'load-balancer-api-internal: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 5.708185ms
      message: 'load-balancer-api-internal: tcp connection to a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 9.526812ms
      message: 'load-balancer-api-internal: resolved host name a7bb57c9b832f468b973bef634922880-71077439c873dcbe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:47:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-network-check-target-ip-10-0-129-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "15296"
    uid: 169f6569-a001-4629-9f04-d92811826c63
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:20Z"
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.022247ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:20Z"
    - latency: 806.526µs
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 953.922µs
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 967.226µs
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 869.057µs
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 3.436096ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 2.235016ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-network-check-target-ip-10-0-137-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "15297"
    uid: 01353ca6-d676-4ad3-b0fd-42f6a4ebeb2f
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:20Z"
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.168604ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:20Z"
    - latency: 1.867277ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 2.096978ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 1.733213ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 1.775445ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 5.441141ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 2.197484ms
      message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-network-check-target-ip-10-0-138-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "15298"
    uid: d330a4e0-ba26-45cf-9d25-f3774bb2922c
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:20Z"
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.191524ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:20Z"
    - latency: 2.168367ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 2.221314ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 2.008237ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 2.08784ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 4.474438ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 2.449906ms
      message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-25-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-25.ec2.internal
      uid: 512526e0-2985-4967-9e6e-3cebf8921739
    resourceVersion: "14795"
    uid: a420b492-e20c-4a9a-9976-23b6203fcd2c
  spec:
    sourcePod: network-check-source-685456655f-p84bm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:51:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.289µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 1.490036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:51:20Z"
    - latency: 839.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 1.571479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:50:20Z"
    - latency: 1.015876ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 1.679242ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:49:20Z"
    - latency: 935.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 1.703669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:48:20Z"
    - latency: 1.53016ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:20Z"
    - latency: 3.700238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:47:20Z"
kind: List
metadata:
  resourceVersion: ""