apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "22880"
    uid: ed264e7b-7e59-4be4-bb14-461a7b725535
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:17:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.435µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:14Z"
    - latency: 841.391µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:14Z"
    - latency: 1.046071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:14Z"
    - latency: 895.164µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:14Z"
    - latency: 1.83278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:14Z"
    - latency: 1.047133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:14Z"
    - latency: 1.379128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "26852"
    uid: c101e527-f55e-42e5-948a-480166598f59
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:16:14Z"
      message: 'load-balancer-api-external: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.811993ms
      message: 'load-balancer-api-external: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:14Z"
    - latency: 6.953642ms
      message: 'load-balancer-api-external: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:22:14Z"
    - latency: 4.669545ms
      message: 'load-balancer-api-external: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:21:14Z"
    - latency: 6.458489ms
      message: 'load-balancer-api-external: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:21:14Z"
    - latency: 3.907724ms
      message: 'load-balancer-api-external: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:20:14Z"
    - latency: 7.576083ms
      message: 'load-balancer-api-external: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:20:14Z"
    - latency: 5.278007ms
      message: 'load-balancer-api-external: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:19:14Z"
    - latency: 6.829646ms
      message: 'load-balancer-api-external: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:19:14Z"
    - latency: 5.171123ms
      message: 'load-balancer-api-external: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:18:14Z"
    - latency: 6.770853ms
      message: 'load-balancer-api-external: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:18:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "26853"
    uid: 00048b35-8488-4e5e-88b0-82e278bdecf2
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:16:14Z"
      message: 'load-balancer-api-internal: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.798915ms
      message: 'load-balancer-api-internal: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:14Z"
    - latency: 7.019783ms
      message: 'load-balancer-api-internal: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:22:14Z"
    - latency: 4.642869ms
      message: 'load-balancer-api-internal: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:21:14Z"
    - latency: 6.515549ms
      message: 'load-balancer-api-internal: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:21:14Z"
    - latency: 5.303996ms
      message: 'load-balancer-api-internal: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:20:14Z"
    - latency: 7.618374ms
      message: 'load-balancer-api-internal: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:20:14Z"
    - latency: 5.378295ms
      message: 'load-balancer-api-internal: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:19:14Z"
    - latency: 6.903203ms
      message: 'load-balancer-api-internal: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:19:14Z"
    - latency: 8.44042ms
      message: 'load-balancer-api-internal: tcp connection to ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:18:14Z"
    - latency: 6.821821ms
      message: 'load-balancer-api-internal: resolved host name ad511c6f613844c26a23adb1d762643b-bea3d6927d9a7e1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:18:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-network-check-target-ip-10-0-133-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "22876"
    uid: ac691983-1680-441e-a34f-9e8a9abada41
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:17:14Z"
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 767.292µs
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:14Z"
    - latency: 843.864µs
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:14Z"
    - latency: 1.278877ms
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:14Z"
    - latency: 773.32µs
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:14Z"
    - latency: 5.104195ms
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:14Z"
    - latency: 849.387µs
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:14Z"
    - latency: 1.02977ms
      message: 'network-check-target-ip-10-0-133-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-network-check-target-ip-10-0-137-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "22877"
    uid: 9e21427b-d48a-49fd-b2b5-b22726260525
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:17:14Z"
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.197081ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:14Z"
    - latency: 2.168318ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:14Z"
    - latency: 2.249122ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:14Z"
    - latency: 2.183789ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:14Z"
    - latency: 2.999005ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:14Z"
    - latency: 2.059429ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:14Z"
    - latency: 2.383664ms
      message: 'network-check-target-ip-10-0-137-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-network-check-target-ip-10-0-140-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "22878"
    uid: f5e2a154-49ef-43d8-b9f4-b5df0bcd0bef
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:17:14Z"
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.151554ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:14Z"
    - latency: 2.258843ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:14Z"
    - latency: 2.296275ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:14Z"
    - latency: 2.120861ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:14Z"
    - latency: 3.480504ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:14Z"
    - latency: 2.063627ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:14Z"
    - latency: 2.708209ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:10:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-18-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-18.ec2.internal
      uid: e0b52f12-abe3-4076-b61a-0862cda0983c
    resourceVersion: "26851"
    uid: c6556368-b6ea-4e03-a39a-9e63469a8428
  spec:
    sourcePod: network-check-source-685456655f-nzjj6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:16:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.789µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:14Z"
    - latency: 1.775582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:22:14Z"
    - latency: 929.271µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:21:14Z"
    - latency: 1.683657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:21:14Z"
    - latency: 789.296µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:20:14Z"
    - latency: 1.945791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:20:14Z"
    - latency: 873.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:19:14Z"
    - latency: 1.868ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:19:14Z"
    - latency: 819.2µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:18:14Z"
    - latency: 1.870409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:18:14Z"
kind: List
metadata:
  resourceVersion: ""