apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "25208"
    uid: 7d12d487-44ac-48bd-8a14-5ffafc9985ac
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:34:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.413469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:34:27Z"
    - latency: 1.422245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 1.366204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 1.336561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 898.997µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 1.113821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 990.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "24029"
    uid: 6af277bc-2ebd-46e0-863c-fc496343ff45
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:33:27Z"
      message: 'load-balancer-api-external: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.78323ms
      message: 'load-balancer-api-external: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 11.075855ms
      message: 'load-balancer-api-external: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 4.423208ms
      message: 'load-balancer-api-external: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 7.612279ms
      message: 'load-balancer-api-external: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 5.188839ms
      message: 'load-balancer-api-external: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 8.148832ms
      message: 'load-balancer-api-external: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 7.187164ms
      message: 'load-balancer-api-external: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 7.275645ms
      message: 'load-balancer-api-external: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 5.617989ms
      message: 'load-balancer-api-external: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 6.853779ms
      message: 'load-balancer-api-external: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:29:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "24028"
    uid: ddd8b9a1-cdde-4b54-bb50-454264c2fd7c
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:33:27Z"
      message: 'load-balancer-api-internal: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.751851ms
      message: 'load-balancer-api-internal: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 11.140345ms
      message: 'load-balancer-api-internal: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 4.423452ms
      message: 'load-balancer-api-internal: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 7.546398ms
      message: 'load-balancer-api-internal: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 3.937126ms
      message: 'load-balancer-api-internal: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 8.286633ms
      message: 'load-balancer-api-internal: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 6.852862ms
      message: 'load-balancer-api-internal: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 7.300647ms
      message: 'load-balancer-api-internal: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 6.187119ms
      message: 'load-balancer-api-internal: tcp connection to ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 6.874395ms
      message: 'load-balancer-api-internal: resolved host name ac8e4717afa0b41e7aac13b51700f88c-58f6c6a4f829a8d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:29:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-network-check-target-ip-10-0-135-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "25206"
    uid: 6436d497-7663-4df7-b964-bdb0908e784c
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:34:27Z"
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.596368ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:34:27Z"
    - latency: 2.905175ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 2.542228ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 2.108228ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 2.587044ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 2.300246ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 2.442635ms
      message: 'network-check-target-ip-10-0-135-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-network-check-target-ip-10-0-137-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "25205"
    uid: bd5b8e58-1b0a-4b14-a3cf-b172175d198e
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:34:27Z"
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.67678ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:34:27Z"
    - latency: 1.650121ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 1.007052ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 1.077864ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 1.088901ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 961.092µs
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 1.486983ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-network-check-target-ip-10-0-138-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "25207"
    uid: 50df6a76-9c0b-4da6-b2cf-c3d08e52382d
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:34:27Z"
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.889985ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:34:27Z"
    - latency: 2.741828ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 2.381693ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 2.564075ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 2.270633ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 2.208959ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 2.241189ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T18:27:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-96.ec2.internal
      uid: a15d9ed5-b6db-481d-a68e-3e8499aeda32
    resourceVersion: "24027"
    uid: fbad8025-c8e6-4672-ada4-9a04435a9f9a
  spec:
    sourcePod: network-check-source-6947749cfc-8c2vg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T18:33:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.40608ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 2.031013ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:33:27Z"
    - latency: 1.128248ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 2.244987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:32:27Z"
    - latency: 1.244234ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 1.798293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:31:27Z"
    - latency: 899.003µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 1.748843ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:30:27Z"
    - latency: 951.831µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T18:29:27Z"
    - latency: 2.031445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T18:29:27Z"
kind: List
metadata:
  resourceVersion: ""