apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14616"
    uid: a90f64cd-016e-4f26-aceb-ce7436e6ecab
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:37:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.252259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:37:07Z"
    - latency: 767.193µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 1.093038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 839.768µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 1.021038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 1.197827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 822.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:31:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14212"
    uid: 1707cc40-c2da-46a7-8c5e-21da753758a2
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:36:07Z"
      message: 'load-balancer-api-external: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.490084ms
      message: 'load-balancer-api-external: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 7.395563ms
      message: 'load-balancer-api-external: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 5.582258ms
      message: 'load-balancer-api-external: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 8.708074ms
      message: 'load-balancer-api-external: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 4.439311ms
      message: 'load-balancer-api-external: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 6.694376ms
      message: 'load-balancer-api-external: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 4.82757ms
      message: 'load-balancer-api-external: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 6.966475ms
      message: 'load-balancer-api-external: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 4.908704ms
      message: 'load-balancer-api-external: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 7.641472ms
      message: 'load-balancer-api-external: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:32:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14213"
    uid: c7cab580-9515-4335-acca-4a889c073c77
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:36:07Z"
      message: 'load-balancer-api-internal: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.346753ms
      message: 'load-balancer-api-internal: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 7.43416ms
      message: 'load-balancer-api-internal: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 4.665313ms
      message: 'load-balancer-api-internal: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 8.609844ms
      message: 'load-balancer-api-internal: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 4.377205ms
      message: 'load-balancer-api-internal: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 6.741646ms
      message: 'load-balancer-api-internal: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 4.836957ms
      message: 'load-balancer-api-internal: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 6.878909ms
      message: 'load-balancer-api-internal: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 4.723699ms
      message: 'load-balancer-api-internal: tcp connection to a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 7.563707ms
      message: 'load-balancer-api-internal: resolved host name a4db5ab42cead4f3fb85091f860a6237-a1800e6054a64723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:32:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-network-check-target-ip-10-0-129-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14615"
    uid: 4ef12338-5260-4e96-94f2-b84743e6248d
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:37:07Z"
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.30635ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:37:07Z"
    - latency: 2.334804ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 2.24277ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 2.377709ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 2.083158ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 2.148122ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 1.965794ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:31:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-network-check-target-ip-10-0-138-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14614"
    uid: eaa30449-d026-4d8e-87dc-642a3da7e2f8
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:37:07Z"
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.246997ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:37:07Z"
    - latency: 2.482176ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 2.009255ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 1.956348ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 1.924004ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 2.055402ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 2.419171ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:31:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-network-check-target-ip-10-0-138-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14613"
    uid: 117884ed-9fb0-4ed0-972a-6192ebba8499
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:37:07Z"
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.439163ms
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:37:07Z"
    - latency: 1.530556ms
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 1.149134ms
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 810.976µs
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 764.873µs
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 708.218µs
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 1.725038ms
      message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:31:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T06:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-76-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-76.ec2.internal
      uid: 620526f4-9b55-4731-8ab6-53f05fa0f2b1
    resourceVersion: "14211"
    uid: 3f62ae78-7f1e-47aa-ae0d-8708931ed77a
  spec:
    sourcePod: network-check-source-8894fc9bd-gcmqq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T06:36:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.185µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 2.489712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:36:07Z"
    - latency: 830.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 1.638628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:35:07Z"
    - latency: 823.432µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 1.628064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:34:07Z"
    - latency: 782.302µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 1.886649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:33:07Z"
    - latency: 1.044253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T06:32:07Z"
    - latency: 2.074696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T06:32:07Z"
kind: List
metadata:
  resourceVersion: ""