apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14910"
    uid: 6b30d909-a1b8-483c-9f81-43e9304d969c
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:07Z"
    - latency: 1.118886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 1.0301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 1.046756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 909.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 1.009037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 823.727µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14285"
    uid: 6e43e7c8-e265-4cee-ae79-05e7c72330ba
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:07Z"
      message: 'load-balancer-api-external: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.762733ms
      message: 'load-balancer-api-external: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 6.532406ms
      message: 'load-balancer-api-external: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 4.483439ms
      message: 'load-balancer-api-external: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 6.199956ms
      message: 'load-balancer-api-external: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 8.937527ms
      message: 'load-balancer-api-external: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 6.944722ms
      message: 'load-balancer-api-external: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 5.587776ms
      message: 'load-balancer-api-external: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 6.404136ms
      message: 'load-balancer-api-external: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 4.666862ms
      message: 'load-balancer-api-external: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 6.506078ms
      message: 'load-balancer-api-external: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14284"
    uid: 28ef1bbb-ed0f-49c3-8f6d-5d24a410ea72
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:07Z"
      message: 'load-balancer-api-internal: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.230515ms
      message: 'load-balancer-api-internal: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 6.629513ms
      message: 'load-balancer-api-internal: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 8.545328ms
      message: 'load-balancer-api-internal: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 6.26326ms
      message: 'load-balancer-api-internal: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 5.753932ms
      message: 'load-balancer-api-internal: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 6.975489ms
      message: 'load-balancer-api-internal: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 5.734934ms
      message: 'load-balancer-api-internal: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 6.337841ms
      message: 'load-balancer-api-internal: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 4.68059ms
      message: 'load-balancer-api-internal: tcp connection to a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 6.420542ms
      message: 'load-balancer-api-internal: resolved host name a405b3e5423654f0b9cac0435c526a19-12320e6c74a38ea9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-network-check-target-ip-10-0-134-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14908"
    uid: 97afaf69-cd0e-43f1-87ff-4c707b653fb9
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:07Z"
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.769662ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:07Z"
    - latency: 2.132148ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 2.084109ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 2.368319ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 2.625149ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 2.07722ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 2.338053ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-network-check-target-ip-10-0-134-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14909"
    uid: 6e4179f7-33da-4fa1-a1eb-5680d9a7f766
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:07Z"
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.7175ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:07Z"
    - latency: 2.37731ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 2.126786ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 2.43645ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 2.259121ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 2.246981ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 2.114749ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-network-check-target-ip-10-0-140-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14907"
    uid: 8d3a80a7-19df-42f1-bedb-e6a23db05788
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:07Z"
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.036µs
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:07Z"
    - latency: 1.526769ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 886.206µs
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 760.052µs
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 951.679µs
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 956.015µs
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 1.077451ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-57.ec2.internal
      uid: 28907a37-7d23-4cfb-96d8-573f2737c519
    resourceVersion: "14283"
    uid: 22fdd20f-e8fc-4a07-babf-879e8b5c6689
  spec:
    sourcePod: network-check-source-989f8b8dc-mp479
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 2.011897ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:07Z"
    - latency: 819.103µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 1.593487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:07Z"
    - latency: 885.144µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 2.240533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:07Z"
    - latency: 1.093074ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 1.690926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:07Z"
    - latency: 860.982µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:07Z"
    - latency: 1.653824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:07Z"
kind: List
metadata:
  resourceVersion: ""