apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11591"
    uid: 0a894ed3-36d2-42df-8560-ca2609cc2734
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.162µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:38Z"
    - latency: 939.466µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 1.328987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 1.077717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 1.122159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 1.24411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:38Z"
    - latency: 1.305704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11202"
    uid: bf11ac23-19ae-4653-a699-db81d8d5adc4
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:15:38Z"
      message: 'load-balancer-api-external: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.210458ms
      message: 'load-balancer-api-external: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 7.454138ms
      message: 'load-balancer-api-external: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 6.142634ms
      message: 'load-balancer-api-external: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 8.114363ms
      message: 'load-balancer-api-external: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 6.289505ms
      message: 'load-balancer-api-external: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 6.530832ms
      message: 'load-balancer-api-external: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 6.182772ms
      message: 'load-balancer-api-external: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 8.053693ms
      message: 'load-balancer-api-external: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 5.470573ms
      message: 'load-balancer-api-external: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:38Z"
    - latency: 8.97187ms
      message: 'load-balancer-api-external: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11203"
    uid: 370dcc8f-aaca-4ac4-a212-9ab48fd93db3
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:15:38Z"
      message: 'load-balancer-api-internal: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.189384ms
      message: 'load-balancer-api-internal: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 7.441372ms
      message: 'load-balancer-api-internal: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 6.103316ms
      message: 'load-balancer-api-internal: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 8.189643ms
      message: 'load-balancer-api-internal: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 5.101606ms
      message: 'load-balancer-api-internal: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 6.501165ms
      message: 'load-balancer-api-internal: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 6.212177ms
      message: 'load-balancer-api-internal: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 8.142946ms
      message: 'load-balancer-api-internal: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 6.588288ms
      message: 'load-balancer-api-internal: tcp connection to aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:38Z"
    - latency: 9.035273ms
      message: 'load-balancer-api-internal: resolved host name aa6eed4326593438583bb4e60cf0f19e-be3f357aae911bc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-network-check-target-ip-10-0-128-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11597"
    uid: 8f8e6c67-f990-463b-90b6-743d9925c123
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:39Z"
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.910514ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:39Z"
    - latency: 1.709325ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:39Z"
    - latency: 1.87725ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:39Z"
    - latency: 1.675838ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:39Z"
    - latency: 1.956002ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:39Z"
    - latency: 728.992µs
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:39Z"
    - latency: 2.054859ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-network-check-target-ip-10-0-140-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11589"
    uid: de121cd8-58de-4752-a8bf-235cf89d5f6e
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:38Z"
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 729.798µs
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:38Z"
    - latency: 1.335221ms
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 1.468971ms
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 931.134µs
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 857.861µs
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 883.389µs
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:38Z"
    - latency: 1.344098ms
      message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-network-check-target-ip-10-0-140-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11590"
    uid: b42939e6-2ec8-4ae3-89a2-8e94ab7b0d81
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:38Z"
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.120962ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:38Z"
    - latency: 2.163704ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 2.296142ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 2.098293ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 2.517457ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 2.670646ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:38Z"
    - latency: 2.257544ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-232.us-east-2.compute.internal
      uid: e74a03a0-cac9-44a6-ad7f-8dd9c81acc8f
    resourceVersion: "11201"
    uid: 4f7aad96-1fd5-449c-abdf-4d25f16e945c
  spec:
    sourcePod: network-check-source-6f78d59f99-vjznv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:15:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 786.309µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 1.672687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:38Z"
    - latency: 875.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 1.719476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:38Z"
    - latency: 801.36µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 1.659863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:38Z"
    - latency: 930.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 1.716107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:38Z"
    - latency: 2.046181ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:38Z"
    - latency: 1.723719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:38Z"
kind: List
metadata:
  resourceVersion: ""