apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "14310"
    uid: 76a187d2-25eb-4900-b00f-c6aca8fff6eb
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:03:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.058428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:57Z"
    - latency: 801.692µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 1.280954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 962.986µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 1.162839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 973.932µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 1.30795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:57:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "13980"
    uid: 0303f7c7-fe90-4bda-9c01-09392010dd11
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:02:57Z"
      message: 'load-balancer-api-external: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.288885ms
      message: 'load-balancer-api-external: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 11.015343ms
      message: 'load-balancer-api-external: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 4.129562ms
      message: 'load-balancer-api-external: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 8.286369ms
      message: 'load-balancer-api-external: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 3.765051ms
      message: 'load-balancer-api-external: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 7.88269ms
      message: 'load-balancer-api-external: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 4.126505ms
      message: 'load-balancer-api-external: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 9.4951ms
      message: 'load-balancer-api-external: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 5.180431ms
      message: 'load-balancer-api-external: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 7.981775ms
      message: 'load-balancer-api-external: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T02:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "13979"
    uid: aea3a610-f8df-4009-b93b-7fa4e1c3ca90
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:02:57Z"
      message: 'load-balancer-api-internal: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.242699ms
      message: 'load-balancer-api-internal: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 11.093987ms
      message: 'load-balancer-api-internal: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 4.140757ms
      message: 'load-balancer-api-internal: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 8.307068ms
      message: 'load-balancer-api-internal: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 3.732813ms
      message: 'load-balancer-api-internal: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 7.965299ms
      message: 'load-balancer-api-internal: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 4.245643ms
      message: 'load-balancer-api-internal: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 9.521742ms
      message: 'load-balancer-api-internal: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 5.159992ms
      message: 'load-balancer-api-internal: tcp connection to a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 7.989835ms
      message: 'load-balancer-api-internal: resolved host name a33d11bb9977b440caba18f7696a8f8a-d8d51721f1aec5a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T02:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-ip-10-0-128-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "14307"
    uid: a547a133-611c-48de-94a0-82dab8561ef2
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:03:57Z"
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.39516ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:57Z"
    - latency: 2.194912ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 2.013017ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 2.147576ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 2.17312ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 2.273427ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 1.983921ms
      message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:57:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-ip-10-0-133-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "14309"
    uid: bafb76f8-52a1-4eea-9519-05756b808336
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:03:57Z"
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.03644ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:57Z"
    - latency: 1.674273ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 1.804156ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 1.789932ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 1.826688ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 1.784116ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 3.059935ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:57:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-ip-10-0-137-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "14308"
    uid: 0fc46010-339c-4c86-8405-11c18f1d86a1
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:03:57Z"
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.40373ms
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:03:57Z"
    - latency: 985.846µs
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 1.079012ms
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 924.442µs
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 906.737µs
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 976.804µs
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 1.815573ms
      message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:57:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T02:56:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 4c8bc694-653d-4dba-8987-0c0734d837a9
    resourceVersion: "13978"
    uid: cea2e080-9f0a-4e0d-8b82-2b45e2ccd49b
  spec:
    sourcePod: network-check-source-685456655f-wlnm8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T03:02:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 763.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 2.557595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:02:57Z"
    - latency: 1.153317ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 1.671924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:01:57Z"
    - latency: 991.821µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 2.08334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T03:00:57Z"
    - latency: 911.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 1.833158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T02:59:57Z"
    - latency: 770.928µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T02:58:57Z"
    - latency: 1.696043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T02:58:57Z"
kind: List
metadata:
  resourceVersion: ""