apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "24501"
    uid: af5609bf-9e5d-42bc-8236-6ac6304a7240
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:13:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:13:14Z"
    - latency: 848.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:12:14Z"
    - latency: 999.957µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:11:14Z"
    - latency: 1.38769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:10:14Z"
    - latency: 864.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:09:14Z"
    - latency: 893.371µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:08:14Z"
    - latency: 1.096766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:07:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "28366"
    uid: efc6d2b8-8558-4005-a700-652e4cb516b1
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:12:14Z"
      message: 'load-balancer-api-external: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.611714ms
      message: 'load-balancer-api-external: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:18:14Z"
    - latency: 6.40598ms
      message: 'load-balancer-api-external: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:18:14Z"
    - latency: 4.426251ms
      message: 'load-balancer-api-external: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:17:14Z"
    - latency: 6.538212ms
      message: 'load-balancer-api-external: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:17:14Z"
    - latency: 3.962324ms
      message: 'load-balancer-api-external: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:16:14Z"
    - latency: 6.219763ms
      message: 'load-balancer-api-external: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:16:14Z"
    - latency: 3.437316ms
      message: 'load-balancer-api-external: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:15:14Z"
    - latency: 7.1446ms
      message: 'load-balancer-api-external: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:15:14Z"
    - latency: 4.729636ms
      message: 'load-balancer-api-external: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:14:14Z"
    - latency: 9.51567ms
      message: 'load-balancer-api-external: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:14:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "28365"
    uid: 313f9ca2-659d-44c5-910e-bb08245b2e83
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:12:14Z"
      message: 'load-balancer-api-internal: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.606391ms
      message: 'load-balancer-api-internal: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:18:14Z"
    - latency: 6.597938ms
      message: 'load-balancer-api-internal: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:18:14Z"
    - latency: 4.176917ms
      message: 'load-balancer-api-internal: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:17:14Z"
    - latency: 6.483999ms
      message: 'load-balancer-api-internal: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:17:14Z"
    - latency: 4.178257ms
      message: 'load-balancer-api-internal: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:16:14Z"
    - latency: 6.172566ms
      message: 'load-balancer-api-internal: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:16:14Z"
    - latency: 3.385323ms
      message: 'load-balancer-api-internal: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:15:14Z"
    - latency: 7.067957ms
      message: 'load-balancer-api-internal: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:15:14Z"
    - latency: 4.989055ms
      message: 'load-balancer-api-internal: tcp connection to ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:14:14Z"
    - latency: 9.566715ms
      message: 'load-balancer-api-internal: resolved host name ac19e44efc7b64c36af23afec3a07d63-f5b67add7e01d0c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:14:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-network-check-target-ip-10-0-137-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "24499"
    uid: ab669a30-2b00-433a-830b-5cb9e9ba0f8c
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:13:14Z"
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.046251ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:13:14Z"
    - latency: 2.443023ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:12:14Z"
    - latency: 2.221274ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:11:14Z"
    - latency: 2.396874ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:10:14Z"
    - latency: 2.034069ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:09:14Z"
    - latency: 1.941473ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:08:14Z"
    - latency: 2.490096ms
      message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:07:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-network-check-target-ip-10-0-141-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "24498"
    uid: cce61b8e-f74b-454d-9674-3498b12f86aa
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:13:14Z"
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.086µs
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:13:14Z"
    - latency: 1.258452ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:12:14Z"
    - latency: 866.438µs
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:11:14Z"
    - latency: 1.26529ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:10:14Z"
    - latency: 1.753574ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:09:14Z"
    - latency: 929.588µs
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:08:14Z"
    - latency: 1.189451ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:07:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-network-check-target-ip-10-0-142-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "24500"
    uid: 38968fa5-68f0-473f-8ddb-e1704327e2c6
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:13:14Z"
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.360303ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:13:14Z"
    - latency: 2.307652ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:12:14Z"
    - latency: 2.568054ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:11:14Z"
    - latency: 2.333041ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:10:14Z"
    - latency: 2.052442ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:09:14Z"
    - latency: 1.977546ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:08:14Z"
    - latency: 2.376896ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:07:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-146.ec2.internal
      uid: 8cc9189b-7b27-4a49-9bc3-31572d4d493d
    resourceVersion: "28364"
    uid: b31535ed-1309-4c85-a5e9-2891e0c31f69
  spec:
    sourcePod: network-check-source-6f8b768455-5bnrs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:12:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:18:14Z"
    - latency: 1.699756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:18:14Z"
    - latency: 1.149691ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:17:14Z"
    - latency: 1.82382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:17:14Z"
    - latency: 863.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:16:14Z"
    - latency: 1.661349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:16:14Z"
    - latency: 942.22µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:15:14Z"
    - latency: 2.095926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:15:14Z"
    - latency: 796.25µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:14:14Z"
    - latency: 1.718712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:14:14Z"
kind: List
metadata:
  resourceVersion: ""