apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "9373"
    uid: 014b2ac2-5322-4c8f-9551-0d5060dcd94b
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "11393"
    uid: 3c3eba64-c8fb-400a-b0a0-0d4f9e14549f
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:46:05Z"
      message: 'load-balancer-api-external: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.236074ms
      message: 'load-balancer-api-external: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:46:05Z"
    - latency: 5.938913ms
      message: 'load-balancer-api-external: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:46:05Z"
    - latency: 55.024539ms
      message: 'load-balancer-api-external: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:45:05Z"
    - latency: 7.218068ms
      message: 'load-balancer-api-external: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:45:05Z"
    - latency: 53.549313ms
      message: 'load-balancer-api-external: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:44:05Z"
    - latency: 6.834998ms
      message: 'load-balancer-api-external: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:44:05Z"
    - latency: 54.902858ms
      message: 'load-balancer-api-external: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:05Z"
    - latency: 6.357925ms
      message: 'load-balancer-api-external: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:43:05Z"
    - latency: 57.640733ms
      message: 'load-balancer-api-external: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:05Z"
    - latency: 5.263122ms
      message: 'load-balancer-api-external: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:42:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "11394"
    uid: 381d1f1c-f00e-47ea-a944-74124cda4999
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:46:05Z"
      message: 'load-balancer-api-internal: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.340818ms
      message: 'load-balancer-api-internal: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:46:05Z"
    - latency: 5.889719ms
      message: 'load-balancer-api-internal: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:46:05Z"
    - latency: 55.013306ms
      message: 'load-balancer-api-internal: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:45:05Z"
    - latency: 7.146207ms
      message: 'load-balancer-api-internal: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:45:05Z"
    - latency: 53.53787ms
      message: 'load-balancer-api-internal: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:44:05Z"
    - latency: 6.76291ms
      message: 'load-balancer-api-internal: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:44:05Z"
    - latency: 53.609997ms
      message: 'load-balancer-api-internal: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:05Z"
    - latency: 6.293313ms
      message: 'load-balancer-api-internal: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:43:05Z"
    - latency: 57.650859ms
      message: 'load-balancer-api-internal: tcp connection to ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:05Z"
    - latency: 5.153676ms
      message: 'load-balancer-api-internal: resolved host name ade6de2a021f44abf894d16992fafbe5-10c28b6b077437af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:42:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-network-check-target-ip-10-0-129-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "9371"
    uid: 4e3014c5-d159-48ab-8998-847a1e10609e
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-network-check-target-ip-10-0-130-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "9372"
    uid: a218d66b-7ce6-4d72-be2e-be2039417c2f
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-network-check-target-ip-10-0-139-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "9369"
    uid: 3dc24794-9e0f-4089-9f07-49be0972d736
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-187.us-west-1.compute.internal
      uid: a96d1e02-359b-464c-bff6-db2a05d3d145
    resourceVersion: "11392"
    uid: 6b745eef-ebbb-4b54-899d-d690ef937aeb
  spec:
    sourcePod: network-check-source-6f78d59f99-b7x57
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:46:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:46:05Z"
    - latency: 1.61298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:46:05Z"
    - latency: 1.061921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:45:05Z"
    - latency: 1.750667ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:45:05Z"
    - latency: 917.729µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:44:05Z"
    - latency: 1.493164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:44:05Z"
    - latency: 803.368µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:05Z"
    - latency: 1.738883ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:43:05Z"
    - latency: 1.242986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:05Z"
    - latency: 1.827861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:42:05Z"
kind: List
metadata:
  resourceVersion: ""