apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14506"
    uid: 4f2c0dfb-9bb2-4880-b3d5-adeab35d1c91
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:04:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.056933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:04:00Z"
    - latency: 988.287µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 1.267508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 1.017811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 1.031123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 992.228µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 915.053µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14082"
    uid: 773169e8-be37-4f0b-97da-07afd2fc62c9
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:03:00Z"
      message: 'load-balancer-api-external: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.998475ms
      message: 'load-balancer-api-external: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 8.239699ms
      message: 'load-balancer-api-external: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 5.090784ms
      message: 'load-balancer-api-external: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 7.990682ms
      message: 'load-balancer-api-external: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 4.649337ms
      message: 'load-balancer-api-external: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 8.437308ms
      message: 'load-balancer-api-external: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 5.437216ms
      message: 'load-balancer-api-external: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 8.113099ms
      message: 'load-balancer-api-external: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 4.104604ms
      message: 'load-balancer-api-external: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 8.445855ms
      message: 'load-balancer-api-external: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:59:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14081"
    uid: 475a0629-42c4-4809-834f-3dcc514973c5
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:03:00Z"
      message: 'load-balancer-api-internal: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.011957ms
      message: 'load-balancer-api-internal: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 8.302672ms
      message: 'load-balancer-api-internal: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 5.149566ms
      message: 'load-balancer-api-internal: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 7.94254ms
      message: 'load-balancer-api-internal: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 4.626881ms
      message: 'load-balancer-api-internal: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 8.521093ms
      message: 'load-balancer-api-internal: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 5.035599ms
      message: 'load-balancer-api-internal: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 8.05949ms
      message: 'load-balancer-api-internal: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 4.653087ms
      message: 'load-balancer-api-internal: tcp connection to ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 8.46177ms
      message: 'load-balancer-api-internal: resolved host name ade6df74683454b6fb9077b59737b36c-23f0564c4c467822.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:59:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-network-check-target-ip-10-0-131-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14503"
    uid: f1c3c10b-46a1-459f-90d2-80d25ad7635e
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:04:00Z"
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.509711ms
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:04:00Z"
    - latency: 980.435µs
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 809.688µs
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 869.81µs
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 895.737µs
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 1.682969ms
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 1.616151ms
      message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-network-check-target-ip-10-0-137-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14504"
    uid: 2bf4eb73-733e-4feb-9bd2-457c32d943b4
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:04:00Z"
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.752117ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:04:00Z"
    - latency: 1.885768ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 1.794388ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 1.977387ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 1.959947ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 2.380164ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 2.135291ms
      message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-network-check-target-ip-10-0-141-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14505"
    uid: 9fcdbc68-070e-4d24-9b29-72fd8f793718
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:04:00Z"
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.998936ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:04:00Z"
    - latency: 1.900053ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 2.065516ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 1.791807ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 2.058557ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 2.110877ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 2.172811ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:56:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-56.ec2.internal
      uid: 76b890a4-8661-48ed-b3c2-aef01a046bff
    resourceVersion: "14080"
    uid: 4fef7b19-7a1e-4611-923f-44dae8c6199d
  spec:
    sourcePod: network-check-source-56d84b9f44-4czjk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:03:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.000003ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 1.791389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:03:00Z"
    - latency: 734.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 2.265205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:02:00Z"
    - latency: 1.026705ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 1.815304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:01:00Z"
    - latency: 4.39616ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 1.634213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:00:00Z"
    - latency: 933.328µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:59:00Z"
    - latency: 1.815518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:59:00Z"
kind: List
metadata:
  resourceVersion: ""