apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "18155"
    uid: 787cef7b-1e69-4e05-9f4e-7110db63222d
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:07:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.721278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:07:39Z"
    - latency: 901.736µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 1.546366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 1.263869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 1.013213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 1.385699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 1.06066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "15334"
    uid: 3690b458-cbcc-424a-8b79-232e7ed7f14c
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:06:39Z"
      message: 'load-balancer-api-external: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.733394ms
      message: 'load-balancer-api-external: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 8.344269ms
      message: 'load-balancer-api-external: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 22.83187ms
      message: 'load-balancer-api-external: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 9.208481ms
      message: 'load-balancer-api-external: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 4.496372ms
      message: 'load-balancer-api-external: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 9.269212ms
      message: 'load-balancer-api-external: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 8.994955ms
      message: 'load-balancer-api-external: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 9.017623ms
      message: 'load-balancer-api-external: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 5.087487ms
      message: 'load-balancer-api-external: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 7.916932ms
      message: 'load-balancer-api-external: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "15335"
    uid: c4aaf39c-b0f7-4172-a27d-2955ebb3ba89
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:06:39Z"
      message: 'load-balancer-api-internal: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.363856ms
      message: 'load-balancer-api-internal: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 8.300399ms
      message: 'load-balancer-api-internal: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 13.155053ms
      message: 'load-balancer-api-internal: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 9.269265ms
      message: 'load-balancer-api-internal: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 4.047414ms
      message: 'load-balancer-api-internal: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 9.288179ms
      message: 'load-balancer-api-internal: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 8.976368ms
      message: 'load-balancer-api-internal: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 8.974018ms
      message: 'load-balancer-api-internal: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 5.052235ms
      message: 'load-balancer-api-internal: tcp connection to a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 8.039019ms
      message: 'load-balancer-api-internal: resolved host name a0665732567c84ebfb899423095a63d9-d34a55c27b5aeec0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-network-check-target-ip-10-0-129-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "18154"
    uid: a577cb13-20d8-451e-8d5e-1b83c792fe7e
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:07:39Z"
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.494723ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:07:39Z"
    - latency: 2.245415ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 2.344966ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 2.333967ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 2.219888ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 4.362869ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 2.224234ms
      message: 'network-check-target-ip-10-0-129-106: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-network-check-target-ip-10-0-129-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "18153"
    uid: c1e43540-a489-45b5-8496-ed6bd47bb446
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:07:39Z"
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.612µs
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:07:39Z"
    - latency: 804.777µs
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 818.612µs
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 847.185µs
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 772.745µs
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 4.393143ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 1.301329ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-network-check-target-ip-10-0-129-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "18152"
    uid: 6ae57aa8-9f7c-4c9e-8e65-2c2141a58e28
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:07:39Z"
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.863157ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:07:39Z"
    - latency: 2.147535ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 2.107847ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 2.061062ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 1.856882ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 1.976357ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 2.026454ms
      message: 'network-check-target-ip-10-0-129-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:00:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-157-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-157.ec2.internal
      uid: 9a4fa4b8-2213-40e6-b17f-b388e4035f8b
    resourceVersion: "15331"
    uid: 8fc6b0dc-0f1c-4422-b0a9-0e99a48412cc
  spec:
    sourcePod: network-check-source-6f8b768455-jgnsf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:06:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.521µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 1.879566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:06:39Z"
    - latency: 907.706µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 2.051381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:05:39Z"
    - latency: 972.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 1.853906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:04:39Z"
    - latency: 1.100921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 1.579781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:03:39Z"
    - latency: 821.338µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:39Z"
    - latency: 1.882525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:02:39Z"
kind: List
metadata:
  resourceVersion: ""