apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "15019"
    uid: d3520d44-9eac-489b-a754-1ebbd4974b41
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:41:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.15472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:24Z"
    - latency: 791.969µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 1.660588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 1.160002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 1.31532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 1.04459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 1.049728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "14550"
    uid: 31a222ac-59ce-461a-b127-ec83f7a86f18
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:40:24Z"
      message: 'load-balancer-api-external: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.815696ms
      message: 'load-balancer-api-external: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 6.677742ms
      message: 'load-balancer-api-external: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 4.762791ms
      message: 'load-balancer-api-external: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 9.881398ms
      message: 'load-balancer-api-external: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 4.490584ms
      message: 'load-balancer-api-external: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 7.312226ms
      message: 'load-balancer-api-external: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 4.958716ms
      message: 'load-balancer-api-external: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 9.074555ms
      message: 'load-balancer-api-external: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 5.252322ms
      message: 'load-balancer-api-external: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 10.540562ms
      message: 'load-balancer-api-external: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:36:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "14549"
    uid: 8c58415d-ba48-4d0f-bc64-9e9e8cfc3413
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:40:24Z"
      message: 'load-balancer-api-internal: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.401073ms
      message: 'load-balancer-api-internal: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 6.543158ms
      message: 'load-balancer-api-internal: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 4.726001ms
      message: 'load-balancer-api-internal: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 9.626636ms
      message: 'load-balancer-api-internal: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 4.508096ms
      message: 'load-balancer-api-internal: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 7.344697ms
      message: 'load-balancer-api-internal: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 4.429585ms
      message: 'load-balancer-api-internal: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 8.444413ms
      message: 'load-balancer-api-internal: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 5.2538ms
      message: 'load-balancer-api-internal: tcp connection to aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 10.417868ms
      message: 'load-balancer-api-internal: resolved host name aa4b262409b7f451e86a7164258738f6-8508c0f89fe61813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:36:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-network-check-target-ip-10-0-133-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "15016"
    uid: 6ae28dd0-cb1d-4c76-b9d7-00b01ba14ea2
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:41:24Z"
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090954ms
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:24Z"
    - latency: 765.422µs
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 1.250494ms
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 881.56µs
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 1.015233ms
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 996.613µs
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 1.2095ms
      message: 'network-check-target-ip-10-0-133-138: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-network-check-target-ip-10-0-134-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "15017"
    uid: 095c029f-6f38-4cf7-bcaa-c19c7e90caeb
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:41:24Z"
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242596ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:24Z"
    - latency: 2.305268ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 2.450545ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 2.653193ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 1.968268ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 5.830308ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 2.163917ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-network-check-target-ip-10-0-137-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "15018"
    uid: 5e1a77da-6586-441f-a547-7b841a5b31de
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:41:24Z"
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212032ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:24Z"
    - latency: 2.173013ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 2.319415ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 2.122171ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 2.794142ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 2.116637ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 2.415852ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:34:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-138-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-138.ec2.internal
      uid: 344f8eac-f084-4fd5-a5f2-4e648a29cfbf
    resourceVersion: "14548"
    uid: 339f8d11-ca4f-48f9-94f6-b24ced65a372
  spec:
    sourcePod: network-check-source-7f44b6dd87-bc8sq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:40:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.022839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 1.911385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:40:24Z"
    - latency: 1.406428ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 1.893434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:39:24Z"
    - latency: 943.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 1.748717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:38:24Z"
    - latency: 916.546µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 1.875769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:37:24Z"
    - latency: 748.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:24Z"
    - latency: 5.27882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:36:24Z"
kind: List
metadata:
  resourceVersion: ""