apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "11310"
    uid: c779373d-4fff-478f-ac9f-5b7f214a44dc
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "14952"
    uid: 79b652e7-a254-474c-a437-6a73112f8394
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:14:15Z"
      message: 'load-balancer-api-external: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.322657ms
      message: 'load-balancer-api-external: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:14:15Z"
    - latency: 10.628624ms
      message: 'load-balancer-api-external: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:14:15Z"
    - latency: 4.910978ms
      message: 'load-balancer-api-external: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:13:15Z"
    - latency: 10.096783ms
      message: 'load-balancer-api-external: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:13:15Z"
    - latency: 4.555187ms
      message: 'load-balancer-api-external: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:12:15Z"
    - latency: 9.328733ms
      message: 'load-balancer-api-external: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:12:15Z"
    - latency: 4.673795ms
      message: 'load-balancer-api-external: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:11:15Z"
    - latency: 8.708037ms
      message: 'load-balancer-api-external: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:11:15Z"
    - latency: 5.003485ms
      message: 'load-balancer-api-external: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:10:15Z"
    - latency: 7.552889ms
      message: 'load-balancer-api-external: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:10:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "14951"
    uid: ce51c178-ae3f-48b5-980f-af72fe5f9ccc
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:14:15Z"
      message: 'load-balancer-api-internal: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.312025ms
      message: 'load-balancer-api-internal: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:14:15Z"
    - latency: 10.56343ms
      message: 'load-balancer-api-internal: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:14:15Z"
    - latency: 4.628476ms
      message: 'load-balancer-api-internal: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:13:15Z"
    - latency: 10.009422ms
      message: 'load-balancer-api-internal: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:13:15Z"
    - latency: 4.640671ms
      message: 'load-balancer-api-internal: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:12:15Z"
    - latency: 9.288776ms
      message: 'load-balancer-api-internal: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:12:15Z"
    - latency: 4.633174ms
      message: 'load-balancer-api-internal: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:11:15Z"
    - latency: 8.794251ms
      message: 'load-balancer-api-internal: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:11:15Z"
    - latency: 3.989615ms
      message: 'load-balancer-api-internal: tcp connection to ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:10:15Z"
    - latency: 7.476934ms
      message: 'load-balancer-api-internal: resolved host name ac04bfbb8264c4050abd287d851529c2-6be01706d72a20b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:10:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-ip-10-0-132-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "11316"
    uid: b445b22a-e416-4a2b-a7a2-e8c566460afd
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-ip-10-0-141-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "11317"
    uid: eb78eea0-4f2d-4d01-a482-1572b200b9c4
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-ip-10-0-143-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "11315"
    uid: c8dc4ec2-3d6d-4af8-b0d3-7f981350dba1
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:08:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 6dce23a1-3712-4df4-aee2-375897cb1908
    resourceVersion: "14950"
    uid: c0f503d4-2fc9-465d-b02a-a2c6e8ec726b
  spec:
    sourcePod: network-check-source-7d88cb55d8-t9xnf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:14:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 689.215µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:14:15Z"
    - latency: 3.052328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:14:15Z"
    - latency: 821.658µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:13:15Z"
    - latency: 1.92197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:13:15Z"
    - latency: 1.002051ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:12:15Z"
    - latency: 2.137085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:12:15Z"
    - latency: 932.822µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:11:15Z"
    - latency: 2.051489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:11:15Z"
    - latency: 1.196061ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:10:15Z"
    - latency: 1.597928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:10:15Z"
kind: List
metadata:
  resourceVersion: ""