apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "23313"
    uid: ae91b305-0fd9-4d6a-b4d2-170dbb18b281
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:14:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.122883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:14:22Z"
    - latency: 826.571µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 986.442µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 873.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 1.041044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 1.273709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 1.058449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:08:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "22018"
    uid: dd562ca9-4a9c-4996-9397-e5ff06188fe7
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:13:22Z"
      message: 'load-balancer-api-external: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.928209ms
      message: 'load-balancer-api-external: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 8.132247ms
      message: 'load-balancer-api-external: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 3.370877ms
      message: 'load-balancer-api-external: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 8.798243ms
      message: 'load-balancer-api-external: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 4.703175ms
      message: 'load-balancer-api-external: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 7.934561ms
      message: 'load-balancer-api-external: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 5.733918ms
      message: 'load-balancer-api-external: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 8.498194ms
      message: 'load-balancer-api-external: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 4.356613ms
      message: 'load-balancer-api-external: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 9.485344ms
      message: 'load-balancer-api-external: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:09:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "22017"
    uid: 39287efa-e2d4-4f29-bbd3-ba703ba1849c
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:13:22Z"
      message: 'load-balancer-api-internal: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.623017ms
      message: 'load-balancer-api-internal: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 8.063121ms
      message: 'load-balancer-api-internal: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 3.363467ms
      message: 'load-balancer-api-internal: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 8.764043ms
      message: 'load-balancer-api-internal: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 5.251075ms
      message: 'load-balancer-api-internal: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 7.892494ms
      message: 'load-balancer-api-internal: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 5.72416ms
      message: 'load-balancer-api-internal: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 8.479797ms
      message: 'load-balancer-api-internal: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 6.028245ms
      message: 'load-balancer-api-internal: tcp connection to a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 9.447313ms
      message: 'load-balancer-api-internal: resolved host name a29f62533fe4548d0b9ccfe6c5783cf7-2d003bdb35da8e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:09:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-network-check-target-ip-10-0-128-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "23310"
    uid: 96f498c9-7545-477c-977d-099309d4501f
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:14:22Z"
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.183046ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:14:22Z"
    - latency: 873.969µs
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 980.247µs
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 934.955µs
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 1.009874ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 1.113186ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 1.461754ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:08:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-network-check-target-ip-10-0-135-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "23311"
    uid: d1804169-7a36-4801-b229-854401fdde77
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:14:22Z"
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.546488ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:14:22Z"
    - latency: 2.174869ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 2.252786ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 2.158576ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 2.147654ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 1.96783ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 2.634158ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:08:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-network-check-target-ip-10-0-140-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "23312"
    uid: 6fa019df-2f64-42e8-981f-ed14e1eb59cd
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:14:22Z"
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.60585ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:14:22Z"
    - latency: 2.510452ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 2.236991ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 2.095664ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 2.131846ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 2.001886ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 2.681681ms
      message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:08:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:07:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-194-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-194.ec2.internal
      uid: 47403750-5378-407f-a55f-4ad840929c9f
    resourceVersion: "22015"
    uid: 6853108a-11d8-4217-b9c2-a2d7831d7004
  spec:
    sourcePod: network-check-source-7cbc45fddc-clsqj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:13:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.269µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 1.622557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:13:22Z"
    - latency: 869.95µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 1.7595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:12:22Z"
    - latency: 855.242µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 1.689054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:11:22Z"
    - latency: 825.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 1.810389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:10:22Z"
    - latency: 843.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:09:22Z"
    - latency: 1.99062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:09:22Z"
kind: List
metadata:
  resourceVersion: ""