apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14721"
    uid: f38307fb-3444-41d5-8fcf-9026ca257b55
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:43:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.106545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:43:48Z"
    - latency: 1.394892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 878.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 848.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 747.922µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 768.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 996.677µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:37:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14265"
    uid: d4c627ad-bcde-4fa8-aee0-fa60c7fc6f39
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:42:48Z"
      message: 'load-balancer-api-external: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.50273ms
      message: 'load-balancer-api-external: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 9.509646ms
      message: 'load-balancer-api-external: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 5.712581ms
      message: 'load-balancer-api-external: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 8.064512ms
      message: 'load-balancer-api-external: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 4.768202ms
      message: 'load-balancer-api-external: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 8.237161ms
      message: 'load-balancer-api-external: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 5.003833ms
      message: 'load-balancer-api-external: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 7.926578ms
      message: 'load-balancer-api-external: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 7.788191ms
      message: 'load-balancer-api-external: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 8.564704ms
      message: 'load-balancer-api-external: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:38:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14266"
    uid: 394a7226-8110-4310-a731-b1acab97a2a9
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:42:48Z"
      message: 'load-balancer-api-internal: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.541263ms
      message: 'load-balancer-api-internal: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 9.287961ms
      message: 'load-balancer-api-internal: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 5.672108ms
      message: 'load-balancer-api-internal: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 8.114091ms
      message: 'load-balancer-api-internal: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 6.625862ms
      message: 'load-balancer-api-internal: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 8.141837ms
      message: 'load-balancer-api-internal: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 4.737793ms
      message: 'load-balancer-api-internal: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 7.975546ms
      message: 'load-balancer-api-internal: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 7.745468ms
      message: 'load-balancer-api-internal: tcp connection to a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 8.620345ms
      message: 'load-balancer-api-internal: resolved host name a8e6d54002ebc4681b18b4f631f489ca-a9ca596ffea9ba66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:38:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-network-check-target-ip-10-0-134-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14719"
    uid: efee7c19-b525-4897-a5dc-0b418fb5e003
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:43:48Z"
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.048606ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:43:48Z"
    - latency: 2.024965ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 2.216111ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 2.286464ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 2.396622ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 2.037077ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 2.169005ms
      message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:37:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-network-check-target-ip-10-0-136-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14720"
    uid: 58672027-803e-4b87-b84f-f1599b2ba18f
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:43:48Z"
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.221676ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:43:48Z"
    - latency: 2.527043ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 2.024614ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 2.134295ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 1.766733ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 2.005989ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 2.459194ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:37:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-network-check-target-ip-10-0-138-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14718"
    uid: 40ad6094-233e-4a59-a0bc-15fbd378c1ae
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:43:48Z"
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.506579ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:43:48Z"
    - latency: 1.300003ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 774.188µs
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 1.415574ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 932.977µs
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 747.562µs
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 1.37978ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:37:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T08:36:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-183.ec2.internal
      uid: 7e3d26f5-c8ef-4c31-a5ad-fc4020ab7474
    resourceVersion: "14264"
    uid: f7e8ab04-a694-4af4-91a7-859ae6c5b910
  spec:
    sourcePod: network-check-source-7d88cb55d8-q2gpm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T08:42:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 1.896894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:42:48Z"
    - latency: 844.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 1.53883ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:41:48Z"
    - latency: 1.101087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 1.894494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:40:48Z"
    - latency: 904.284µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 1.5481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:39:48Z"
    - latency: 1.201465ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T08:38:48Z"
    - latency: 1.660697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T08:38:48Z"
kind: List
metadata:
  resourceVersion: ""