apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11891"
    uid: 71147ff0-b691-4ba5-987b-87ce5797e95a
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.588336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:40Z"
    - latency: 1.091293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 1.287819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 1.040753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 1.12833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 910.39µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 1.041186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:37:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11701"
    uid: 4499b4b9-9a25-4517-825d-ef6085fcd57c
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:42:40Z"
      message: 'load-balancer-api-external: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 62.134038ms
      message: 'load-balancer-api-external: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 7.696216ms
      message: 'load-balancer-api-external: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 61.479777ms
      message: 'load-balancer-api-external: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 7.172315ms
      message: 'load-balancer-api-external: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 54.858672ms
      message: 'load-balancer-api-external: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 6.828431ms
      message: 'load-balancer-api-external: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 52.372417ms
      message: 'load-balancer-api-external: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 7.535245ms
      message: 'load-balancer-api-external: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 53.271386ms
      message: 'load-balancer-api-external: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 10.701907ms
      message: 'load-balancer-api-external: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:38:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11700"
    uid: 25caa60d-bb88-494b-a6f3-24d77a8ed01e
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:42:40Z"
      message: 'load-balancer-api-internal: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.58991ms
      message: 'load-balancer-api-internal: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 7.633945ms
      message: 'load-balancer-api-internal: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 55.467522ms
      message: 'load-balancer-api-internal: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 7.233104ms
      message: 'load-balancer-api-internal: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 54.91017ms
      message: 'load-balancer-api-internal: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 6.779214ms
      message: 'load-balancer-api-internal: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 52.413077ms
      message: 'load-balancer-api-internal: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 7.447387ms
      message: 'load-balancer-api-internal: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 53.297265ms
      message: 'load-balancer-api-internal: tcp connection to ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 10.634184ms
      message: 'load-balancer-api-internal: resolved host name ad8c94ae8ab13402e9b9d59431970256-321e80316cff2f8b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:38:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-network-check-target-ip-10-0-130-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11890"
    uid: b5536dcf-3c04-4a20-90df-2b729d107c66
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:40Z"
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.95701ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:40Z"
    - latency: 2.331448ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 1.876007ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 1.798887ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 1.587845ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 1.86245ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 2.075289ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:37:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-network-check-target-ip-10-0-136-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11888"
    uid: d1332b73-5b89-4d88-8df3-d5ce68e07cf5
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:40Z"
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.666µs
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:40Z"
    - latency: 849.476µs
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 1.589611ms
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 1.118947ms
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 786.811µs
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 1.377101ms
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 1.335913ms
      message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:37:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-network-check-target-ip-10-0-142-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11889"
    uid: 28002490-dc09-489f-aeeb-5ff0e855fd0b
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:40Z"
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.563884ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:40Z"
    - latency: 1.962907ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 1.989454ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 2.056742ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 2.044487ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 1.989579ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 2.288899ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:37:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:36:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-83.us-west-1.compute.internal
      uid: 4150db69-0f1a-47e5-8ba5-5412a2ff3156
    resourceVersion: "11699"
    uid: 888eacb3-5b98-495f-a4c3-acf167499971
  spec:
    sourcePod: network-check-source-6f78d59f99-7v98h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:42:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 725.708µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 1.768472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:40Z"
    - latency: 798.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 1.605963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:40Z"
    - latency: 1.011699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 1.780009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:40:40Z"
    - latency: 908.669µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 1.781263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:39:40Z"
    - latency: 961.957µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:38:40Z"
    - latency: 1.935039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:38:40Z"
kind: List
metadata:
  resourceVersion: ""