apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "14282"
    uid: 58088ae0-582a-4459-8431-c2ebc2f48adc
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:13:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.789µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:13:17Z"
    - latency: 876.121µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 1.035334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 898.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 885.194µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 861.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 1.002443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:07:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "13878"
    uid: e0d76bca-8455-4021-8efc-292b14344548
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:12:17Z"
      message: 'load-balancer-api-external: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.133948ms
      message: 'load-balancer-api-external: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 8.604133ms
      message: 'load-balancer-api-external: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 4.776203ms
      message: 'load-balancer-api-external: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 7.909046ms
      message: 'load-balancer-api-external: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 4.953731ms
      message: 'load-balancer-api-external: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 7.824834ms
      message: 'load-balancer-api-external: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 4.650785ms
      message: 'load-balancer-api-external: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 7.828854ms
      message: 'load-balancer-api-external: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 3.812962ms
      message: 'load-balancer-api-external: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 9.008262ms
      message: 'load-balancer-api-external: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:08:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "13877"
    uid: dae89bd2-7f8d-4368-9f38-373d59ee869f
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:12:17Z"
      message: 'load-balancer-api-internal: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.095117ms
      message: 'load-balancer-api-internal: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 8.631726ms
      message: 'load-balancer-api-internal: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 4.745276ms
      message: 'load-balancer-api-internal: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 7.937135ms
      message: 'load-balancer-api-internal: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 5.156919ms
      message: 'load-balancer-api-internal: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 7.841232ms
      message: 'load-balancer-api-internal: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 4.648342ms
      message: 'load-balancer-api-internal: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 7.844346ms
      message: 'load-balancer-api-internal: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 4.713542ms
      message: 'load-balancer-api-internal: tcp connection to adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 9.024275ms
      message: 'load-balancer-api-internal: resolved host name adfd4c40e32074dada089255f2d4ea4b-5ff18cd5a6b1da21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:08:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-network-check-target-ip-10-0-137-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "14280"
    uid: e0fe3ba3-806e-47b0-83b1-6e6ec1c49ba6
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:13:17Z"
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.481383ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:13:17Z"
    - latency: 2.515819ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 2.322526ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 2.059027ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 2.382215ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 2.403565ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 2.432819ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:07:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-network-check-target-ip-10-0-143-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "14281"
    uid: e3127158-cbca-4f49-b798-e88b542fe936
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:13:17Z"
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.184485ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:13:17Z"
    - latency: 2.422474ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 2.389929ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 2.258483ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 2.109614ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 2.34554ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 2.439403ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:07:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-network-check-target-ip-10-0-143-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "14279"
    uid: 02b3211c-150d-46a0-bfc5-7731226c1cef
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:13:17Z"
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 726.364µs
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:13:17Z"
    - latency: 1.085921ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 790.1µs
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 868.488µs
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 835.266µs
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 888.311µs
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 1.710845ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:07:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T07:06:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-69-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-69.ec2.internal
      uid: 70ad9bf6-b00d-4628-8010-e99eb28b826c
    resourceVersion: "13876"
    uid: 77e12c9a-61b8-480a-87db-e80f247c9ae5
  spec:
    sourcePod: network-check-source-8894fc9bd-qpjps
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T07:12:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.189µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 2.076264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:12:17Z"
    - latency: 826.538µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 1.776574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:11:17Z"
    - latency: 803.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 1.627333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:10:17Z"
    - latency: 864.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 1.669507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:09:17Z"
    - latency: 1.016254ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T07:08:17Z"
    - latency: 1.626765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T07:08:17Z"
kind: List
metadata:
  resourceVersion: ""