apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "14011"
    uid: 3d21cbd7-cb83-43ac-b063-2e85c2aa829b
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:12:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.744µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:12:01Z"
    - latency: 1.067588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:01Z"
    - latency: 867.812µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:01Z"
    - latency: 1.081896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:01Z"
    - latency: 954.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:01Z"
    - latency: 961.447µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:01Z"
    - latency: 985.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "16991"
    uid: fa86258c-8437-485d-afcb-bf90429c1520
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:01Z"
      message: 'load-balancer-api-external: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.98281ms
      message: 'load-balancer-api-external: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:17:01Z"
    - latency: 8.11175ms
      message: 'load-balancer-api-external: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:17:01Z"
    - latency: 3.732085ms
      message: 'load-balancer-api-external: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:16:01Z"
    - latency: 8.6746ms
      message: 'load-balancer-api-external: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:16:01Z"
    - latency: 5.656975ms
      message: 'load-balancer-api-external: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:15:01Z"
    - latency: 7.997146ms
      message: 'load-balancer-api-external: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:15:01Z"
    - latency: 5.079644ms
      message: 'load-balancer-api-external: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:14:01Z"
    - latency: 8.852906ms
      message: 'load-balancer-api-external: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:14:01Z"
    - latency: 5.028393ms
      message: 'load-balancer-api-external: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:13:01Z"
    - latency: 7.656589ms
      message: 'load-balancer-api-external: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:13:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "16992"
    uid: be02df87-273b-4f3f-bb90-22e07c838b26
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:01Z"
      message: 'load-balancer-api-internal: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.911986ms
      message: 'load-balancer-api-internal: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:17:01Z"
    - latency: 8.135596ms
      message: 'load-balancer-api-internal: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:17:01Z"
    - latency: 3.599957ms
      message: 'load-balancer-api-internal: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:16:01Z"
    - latency: 8.578665ms
      message: 'load-balancer-api-internal: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:16:01Z"
    - latency: 5.615742ms
      message: 'load-balancer-api-internal: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:15:01Z"
    - latency: 8.070905ms
      message: 'load-balancer-api-internal: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:15:01Z"
    - latency: 5.671454ms
      message: 'load-balancer-api-internal: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:14:01Z"
    - latency: 8.825677ms
      message: 'load-balancer-api-internal: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:14:01Z"
    - latency: 5.912909ms
      message: 'load-balancer-api-internal: tcp connection to a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:13:01Z"
    - latency: 7.723157ms
      message: 'load-balancer-api-internal: resolved host name a2ab6d1f9e363480e81a4aa1e7d82078-94306bb0fc714e5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:13:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-network-check-target-ip-10-0-129-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "14010"
    uid: 28ba6514-c7eb-42f0-a8cc-a29582269c15
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:12:01Z"
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079317ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:12:01Z"
    - latency: 2.180003ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:01Z"
    - latency: 2.372525ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:01Z"
    - latency: 2.554411ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:01Z"
    - latency: 2.223344ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:01Z"
    - latency: 2.548039ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:01Z"
    - latency: 2.233368ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-network-check-target-ip-10-0-132-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "14009"
    uid: f1192d31-22e8-4193-81e8-978905d43dcb
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:12:01Z"
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079097ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:12:01Z"
    - latency: 2.335237ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:01Z"
    - latency: 1.976561ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:01Z"
    - latency: 2.257675ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:01Z"
    - latency: 1.979168ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:01Z"
    - latency: 2.139902ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:01Z"
    - latency: 2.09041ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-network-check-target-ip-10-0-138-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "14008"
    uid: 1c28ccc9-9353-43d2-912c-a08d5724128a
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:12:01Z"
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 778.826µs
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:12:01Z"
    - latency: 915.451µs
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:01Z"
    - latency: 781.924µs
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:01Z"
    - latency: 1.393899ms
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:01Z"
    - latency: 1.232741ms
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:01Z"
    - latency: 1.214676ms
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:01Z"
    - latency: 1.605567ms
      message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:05:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-88-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-88.ec2.internal
      uid: dd53f6bd-dca3-4e90-8c38-05589156ef12
    resourceVersion: "16990"
    uid: c1757a7c-8819-4fb0-b20b-5b0c2c0f51d7
  spec:
    sourcePod: network-check-source-dbd9cf844-ztclm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 662.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:17:01Z"
    - latency: 1.640184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:17:01Z"
    - latency: 750.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:16:01Z"
    - latency: 2.185609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:16:01Z"
    - latency: 1.206648ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:15:01Z"
    - latency: 1.65191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:15:01Z"
    - latency: 1.099676ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:14:01Z"
    - latency: 1.590019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:14:01Z"
    - latency: 1.142986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:13:01Z"
    - latency: 1.46857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:13:01Z"
kind: List
metadata:
  resourceVersion: ""