apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "23928"
    uid: 3b4e1fbc-3852-47d9-bfd7-b40904d98d61
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:13:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.292056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:13:59Z"
    - latency: 1.092955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 1.107587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 871.839µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 857.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 773.582µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 1.100704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:07:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "22472"
    uid: a424daff-daa7-46c1-8b6c-8e43c518d6d0
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:12:59Z"
      message: 'load-balancer-api-external: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.391762ms
      message: 'load-balancer-api-external: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 6.757092ms
      message: 'load-balancer-api-external: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 4.543517ms
      message: 'load-balancer-api-external: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 7.039684ms
      message: 'load-balancer-api-external: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 4.738561ms
      message: 'load-balancer-api-external: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 7.284725ms
      message: 'load-balancer-api-external: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 4.799857ms
      message: 'load-balancer-api-external: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 7.564731ms
      message: 'load-balancer-api-external: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 3.623244ms
      message: 'load-balancer-api-external: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 7.391806ms
      message: 'load-balancer-api-external: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "22471"
    uid: 542a42a8-32f5-4ca9-b2fc-3678e599c365
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:12:59Z"
      message: 'load-balancer-api-internal: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.47362ms
      message: 'load-balancer-api-internal: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 6.639922ms
      message: 'load-balancer-api-internal: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 4.561077ms
      message: 'load-balancer-api-internal: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 7.221591ms
      message: 'load-balancer-api-internal: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 4.85541ms
      message: 'load-balancer-api-internal: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 7.230849ms
      message: 'load-balancer-api-internal: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 4.310449ms
      message: 'load-balancer-api-internal: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 7.685403ms
      message: 'load-balancer-api-internal: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 4.506496ms
      message: 'load-balancer-api-internal: tcp connection to a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 7.364073ms
      message: 'load-balancer-api-internal: resolved host name a761ba4e65f3f4ed9b09d9498863701a-7b5a62ba71b36915.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-network-check-target-ip-10-0-128-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "23925"
    uid: ee2091d9-c5c9-411a-8a5b-6b3cad6cba50
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:13:59Z"
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.518074ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:13:59Z"
    - latency: 868.289µs
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 1.409249ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 867.233µs
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 1.351017ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 1.465264ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 1.266462ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:07:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-network-check-target-ip-10-0-130-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "23927"
    uid: bd2cc346-023b-426a-b234-d44a7d10bc46
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:13:59Z"
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.888674ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:13:59Z"
    - latency: 2.273686ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 2.065838ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 2.204764ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 2.293649ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 2.223999ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 2.534456ms
      message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:07:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-network-check-target-ip-10-0-134-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "23926"
    uid: c6cbec68-d5ed-4613-b09b-43f24a17249c
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:13:59Z"
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242302ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:13:59Z"
    - latency: 2.529694ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 1.975183ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 2.111705ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 2.194077ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 2.176254ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 2.24368ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:07:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:06:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-28.ec2.internal
      uid: a6b2ba13-04f4-445e-9e08-3539dffc1dd0
    resourceVersion: "22470"
    uid: a3cd34a3-ea7c-4d81-9c9d-8b52512b21d4
  spec:
    sourcePod: network-check-source-685456655f-6ngrs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:12:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.239µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 1.633991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:12:59Z"
    - latency: 1.127184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 1.871509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:11:59Z"
    - latency: 767.659µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 2.143959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:10:59Z"
    - latency: 1.193015ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 2.01287ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:09:59Z"
    - latency: 821.241µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:08:59Z"
    - latency: 2.030337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:08:59Z"
kind: List
metadata:
  resourceVersion: ""