apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "24530"
    uid: 3ef5ce9a-f11a-416c-9db2-c8ef74abaf1a
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:06:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 795.538µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:06:46Z"
    - latency: 860.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:05:46Z"
    - latency: 1.158299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:04:46Z"
    - latency: 1.375004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:03:46Z"
    - latency: 1.224969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:02:46Z"
    - latency: 933.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:01:46Z"
    - latency: 1.158631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:00:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "29372"
    uid: 5b295fbb-814a-4e0a-b526-b9f3bb1d413b
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:05:46Z"
      message: 'load-balancer-api-external: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.411149ms
      message: 'load-balancer-api-external: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:11:46Z"
    - latency: 9.363125ms
      message: 'load-balancer-api-external: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:11:46Z"
    - latency: 4.860426ms
      message: 'load-balancer-api-external: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:10:46Z"
    - latency: 8.620734ms
      message: 'load-balancer-api-external: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:10:46Z"
    - latency: 6.079929ms
      message: 'load-balancer-api-external: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:09:46Z"
    - latency: 7.896317ms
      message: 'load-balancer-api-external: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:09:46Z"
    - latency: 4.300611ms
      message: 'load-balancer-api-external: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:08:46Z"
    - latency: 8.551881ms
      message: 'load-balancer-api-external: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:08:46Z"
    - latency: 4.268596ms
      message: 'load-balancer-api-external: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:07:46Z"
    - latency: 7.95504ms
      message: 'load-balancer-api-external: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "29371"
    uid: 9f12377b-a50e-4614-93d4-4c186829d8ee
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:05:46Z"
      message: 'load-balancer-api-internal: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.435514ms
      message: 'load-balancer-api-internal: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:11:46Z"
    - latency: 9.329943ms
      message: 'load-balancer-api-internal: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:11:46Z"
    - latency: 4.878949ms
      message: 'load-balancer-api-internal: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:10:46Z"
    - latency: 8.597689ms
      message: 'load-balancer-api-internal: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:10:46Z"
    - latency: 5.059831ms
      message: 'load-balancer-api-internal: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:09:46Z"
    - latency: 7.935498ms
      message: 'load-balancer-api-internal: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:09:46Z"
    - latency: 4.215738ms
      message: 'load-balancer-api-internal: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:08:46Z"
    - latency: 8.519898ms
      message: 'load-balancer-api-internal: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:08:46Z"
    - latency: 4.285428ms
      message: 'load-balancer-api-internal: tcp connection to a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:07:46Z"
    - latency: 8.022042ms
      message: 'load-balancer-api-internal: resolved host name a89d10d72a35e4d9bbb557d9f9018691-4cc33a10f09bb723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-network-check-target-ip-10-0-130-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "24529"
    uid: 2e2256f1-a27a-4094-abda-d81e1695218a
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:06:46Z"
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.183619ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:06:46Z"
    - latency: 2.411187ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:05:46Z"
    - latency: 2.329474ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:04:46Z"
    - latency: 2.08535ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:03:46Z"
    - latency: 2.891428ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:02:46Z"
    - latency: 1.712707ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:01:46Z"
    - latency: 2.201073ms
      message: 'network-check-target-ip-10-0-130-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:00:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-network-check-target-ip-10-0-131-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "24528"
    uid: ff3a5806-021d-4ba8-836b-37f0e8595e7f
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:06:46Z"
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.303617ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:06:46Z"
    - latency: 2.326244ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:05:46Z"
    - latency: 2.106835ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:04:46Z"
    - latency: 2.130323ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:03:46Z"
    - latency: 2.470168ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:02:46Z"
    - latency: 2.08383ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:01:46Z"
    - latency: 2.330629ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:00:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-network-check-target-ip-10-0-138-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "24527"
    uid: 06b25a62-a735-4e56-9110-bdc7792b286b
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:06:46Z"
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.196µs
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:06:46Z"
    - latency: 1.011194ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:05:46Z"
    - latency: 1.25531ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:04:46Z"
    - latency: 716.077µs
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:03:46Z"
    - latency: 894.265µs
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:02:46Z"
    - latency: 655.145µs
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:01:46Z"
    - latency: 977.473µs
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:00:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T00:59:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-101.ec2.internal
      uid: a17fcd2d-8c9c-4039-b6e7-2f5dc19e75a2
    resourceVersion: "29370"
    uid: 93ab46b1-deeb-484b-b39f-aeb586ddaadf
  spec:
    sourcePod: network-check-source-7f44b6dd87-xvxlc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:05:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159363ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:11:46Z"
    - latency: 1.685887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:11:46Z"
    - latency: 815.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:10:46Z"
    - latency: 1.84267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:10:46Z"
    - latency: 924.185µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:09:46Z"
    - latency: 1.63036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:09:46Z"
    - latency: 804.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:08:46Z"
    - latency: 2.098947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:08:46Z"
    - latency: 825.783µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T01:07:46Z"
    - latency: 1.776808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T01:07:46Z"
kind: List
metadata:
  resourceVersion: ""