apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14407"
    uid: 2cce0a66-d6b4-4af5-909b-02f3aac7a9fc
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:59:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:59:04Z"
    - latency: 1.126429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 1.266603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 890.74µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 1.053129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 1.04998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 967.061µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14035"
    uid: bb1963a9-280f-40ac-9718-f191c9e4127f
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:58:04Z"
      message: 'load-balancer-api-external: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.037575ms
      message: 'load-balancer-api-external: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 11.321636ms
      message: 'load-balancer-api-external: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 3.958801ms
      message: 'load-balancer-api-external: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 7.865547ms
      message: 'load-balancer-api-external: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 4.378611ms
      message: 'load-balancer-api-external: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 10.983855ms
      message: 'load-balancer-api-external: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 5.141783ms
      message: 'load-balancer-api-external: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 12.419757ms
      message: 'load-balancer-api-external: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 3.896554ms
      message: 'load-balancer-api-external: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 8.287686ms
      message: 'load-balancer-api-external: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:54:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14036"
    uid: 7d3d5878-9083-451f-ad79-8d3b242e561d
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:58:04Z"
      message: 'load-balancer-api-internal: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.14676ms
      message: 'load-balancer-api-internal: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 11.409018ms
      message: 'load-balancer-api-internal: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 4.783666ms
      message: 'load-balancer-api-internal: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 7.799065ms
      message: 'load-balancer-api-internal: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 4.455374ms
      message: 'load-balancer-api-internal: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 10.859159ms
      message: 'load-balancer-api-internal: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 5.140076ms
      message: 'load-balancer-api-internal: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 12.386811ms
      message: 'load-balancer-api-internal: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 4.597747ms
      message: 'load-balancer-api-internal: tcp connection to aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 8.410376ms
      message: 'load-balancer-api-internal: resolved host name aa2492febcc834dad862c64780f05fdf-13c51a5f5f39827b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:54:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-130-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14404"
    uid: f3ed1e0f-3306-45ad-aee9-a51fde980e5d
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:59:04Z"
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.434763ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:59:04Z"
    - latency: 891.14µs
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 809.991µs
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 808.869µs
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 1.674315ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 865.574µs
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 1.560216ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-131-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14405"
    uid: 4237ed40-2e30-41de-9707-1c25e9867abd
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:59:04Z"
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.986313ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:59:04Z"
    - latency: 1.728564ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 1.756042ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 1.61797ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 1.859269ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 1.751476ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 1.73053ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-141-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14406"
    uid: 6a9dc918-91af-4e5c-ab45-a3941a2655a5
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:59:04Z"
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.972636ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:59:04Z"
    - latency: 2.124628ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 2.052224ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 2.075522ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 2.51064ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 2.064152ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 2.265678ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:52:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 7cbfef71-63bc-4fea-8bde-aaabc10087cf
    resourceVersion: "14034"
    uid: 0229aa30-d79a-4771-9ce2-469a403ab762
  spec:
    sourcePod: network-check-source-7f44b6dd87-knxr4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:58:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.542µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 1.790907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:58:04Z"
    - latency: 728.251µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 2.008979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:57:04Z"
    - latency: 4.927483ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 1.998394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:56:04Z"
    - latency: 919.164µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 2.489404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:55:04Z"
    - latency: 859.005µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:54:04Z"
    - latency: 1.953792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:54:04Z"
kind: List
metadata:
  resourceVersion: ""