apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "11000"
    uid: 9667120a-2b9c-4d43-a280-7b3f220e6509
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:21:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.07873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:01Z"
    - latency: 1.025819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 908.517µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 1.071008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 1.062843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 1.038775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 1.452796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "10575"
    uid: d414a2f5-c69b-49d5-aae5-a7ae0a897d71
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:20:01Z"
      message: 'load-balancer-api-external: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.206239ms
      message: 'load-balancer-api-external: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 14.844835ms
      message: 'load-balancer-api-external: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 51.688919ms
      message: 'load-balancer-api-external: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 8.353927ms
      message: 'load-balancer-api-external: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 51.358091ms
      message: 'load-balancer-api-external: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 10.587886ms
      message: 'load-balancer-api-external: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 55.699552ms
      message: 'load-balancer-api-external: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 11.109282ms
      message: 'load-balancer-api-external: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 50.364622ms
      message: 'load-balancer-api-external: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 9.345087ms
      message: 'load-balancer-api-external: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:16:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "10574"
    uid: 6d18b08e-d291-4eb9-ae3a-70638150ca8d
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:20:01Z"
      message: 'load-balancer-api-internal: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.072372ms
      message: 'load-balancer-api-internal: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 14.922693ms
      message: 'load-balancer-api-internal: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 51.720888ms
      message: 'load-balancer-api-internal: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 8.432472ms
      message: 'load-balancer-api-internal: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 55.043587ms
      message: 'load-balancer-api-internal: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 10.617568ms
      message: 'load-balancer-api-internal: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 52.201253ms
      message: 'load-balancer-api-internal: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 10.988686ms
      message: 'load-balancer-api-internal: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 51.629889ms
      message: 'load-balancer-api-internal: tcp connection to a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 9.362681ms
      message: 'load-balancer-api-internal: resolved host name a271bcc655e9a49c29f609f8a7e14462-971c48aa044ba8cd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:16:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-132-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "10998"
    uid: 0216bf66-13ab-4f5d-b85b-f0852ce4ab0c
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:21:01Z"
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.774248ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:01Z"
    - latency: 1.582792ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 876.82µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 1.053392ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 862.159µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 959.67µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 1.75921ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-138-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "10997"
    uid: a8584b5d-bc30-47ac-bd23-f84a5a0c0831
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:21:01Z"
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.36877ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:01Z"
    - latency: 2.193055ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 2.443288ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 2.029678ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 2.205015ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 2.07997ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 2.21466ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-140-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "10999"
    uid: 67ea5781-4fa2-4b99-9cd8-600cb1266ea0
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:21:01Z"
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.040674ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:01Z"
    - latency: 3.05306ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 2.436106ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 2.378839ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 2.584299ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 2.290354ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 2.614547ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:14:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.us-west-2.compute.internal
      uid: 41e5fdb3-77a5-4b18-a2f2-ada4cd1020ad
    resourceVersion: "10572"
    uid: 1c034d86-9124-4f29-a124-089fe2853bca
  spec:
    sourcePod: network-check-source-6f78d59f99-5hgjp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:20:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 1.760095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:20:01Z"
    - latency: 870.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 1.87166ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:19:01Z"
    - latency: 952.928µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 2.224197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:18:01Z"
    - latency: 989.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 1.726349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:17:01Z"
    - latency: 1.107933ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:01Z"
    - latency: 1.666496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:16:01Z"
kind: List
metadata:
  resourceVersion: ""