apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "11018"
    uid: 338307ce-4916-479d-9ad4-8e8ebb6655f8
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "21851"
    uid: a9fe4116-c608-4e15-ac3e-fae9cc341bc5
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:40:25Z"
      message: 'load-balancer-api-external: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.585667ms
      message: 'load-balancer-api-external: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:25Z"
    - latency: 8.744974ms
      message: 'load-balancer-api-external: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:40:25Z"
    - latency: 4.298592ms
      message: 'load-balancer-api-external: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:25Z"
    - latency: 8.713538ms
      message: 'load-balancer-api-external: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:39:25Z"
    - latency: 3.938507ms
      message: 'load-balancer-api-external: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:25Z"
    - latency: 8.309841ms
      message: 'load-balancer-api-external: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:38:25Z"
    - latency: 4.358826ms
      message: 'load-balancer-api-external: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:25Z"
    - latency: 10.272244ms
      message: 'load-balancer-api-external: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:37:25Z"
    - latency: 4.197153ms
      message: 'load-balancer-api-external: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:36:25Z"
    - latency: 8.002842ms
      message: 'load-balancer-api-external: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "21850"
    uid: 0435d51b-8e2f-4856-9d04-7a9467f92df8
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:40:25Z"
      message: 'load-balancer-api-internal: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.139223ms
      message: 'load-balancer-api-internal: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:25Z"
    - latency: 8.779533ms
      message: 'load-balancer-api-internal: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:40:25Z"
    - latency: 4.285629ms
      message: 'load-balancer-api-internal: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:25Z"
    - latency: 8.689466ms
      message: 'load-balancer-api-internal: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:39:25Z"
    - latency: 3.894366ms
      message: 'load-balancer-api-internal: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:25Z"
    - latency: 8.340487ms
      message: 'load-balancer-api-internal: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:38:25Z"
    - latency: 4.344646ms
      message: 'load-balancer-api-internal: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:25Z"
    - latency: 10.29592ms
      message: 'load-balancer-api-internal: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:37:25Z"
    - latency: 3.724213ms
      message: 'load-balancer-api-internal: tcp connection to ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:36:25Z"
    - latency: 8.03659ms
      message: 'load-balancer-api-internal: resolved host name ad649aae524764508880578c2ea584ae-53dad45c7350e0a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-network-check-target-ip-10-0-128-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "11015"
    uid: 27a74ff8-c1e9-43ac-b89e-544d0c45ee3f
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-network-check-target-ip-10-0-134-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "11017"
    uid: 28ebbcc4-8e16-4046-a33c-75df1706d42f
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-network-check-target-ip-10-0-141-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "11016"
    uid: 27eca99e-7bb7-41eb-8f4f-9834336f53e5
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:34:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-84-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-84.ec2.internal
      uid: d1ffdeb8-0431-4b23-9ec0-9b11d322d225
    resourceVersion: "21849"
    uid: 5ced146b-e58a-4448-ab10-2f6867d6c52d
  spec:
    sourcePod: network-check-source-6f8b768455-2tq2k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:40:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.81292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:25Z"
    - latency: 2.265508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:40:25Z"
    - latency: 969.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:25Z"
    - latency: 4.058952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:39:25Z"
    - latency: 870.255µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:25Z"
    - latency: 1.694073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:38:25Z"
    - latency: 913.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:25Z"
    - latency: 1.881682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:37:25Z"
    - latency: 1.151783ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:36:25Z"
    - latency: 1.711488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:36:25Z"
kind: List
metadata:
  resourceVersion: ""