Failed to stat minio object

What happened:

    /home/runner/go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:136
github.com/robfig/cron/v3.(*Cron).startJob.func1
    /home/runner/go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:312
will retrieve newly completed deployments to build insight data
will retrieve all applications to build insight data
failed to stat minio object    {"path": "insights/milestone.json", "error": "not found"}
github.com/pipe-cd/pipecd/pkg/filestore/minio.(*Store).GetReader
    /home/runner/work/pipecd/pipecd/pkg/filestore/minio/minio.go:109
github.com/pipe-cd/pipecd/pkg/filestore/minio.(*Store).Get
    /home/runner/work/pipecd/pipecd/pkg/filestore/minio/minio.go:119
github.com/pipe-cd/pipecd/pkg/insight/insightstore.(*store).GetMilestone
    /home/runner/work/pipecd/pipecd/pkg/insight/insightstore/milestonestore.go:30
github.com/pipe-cd/pipecd/pkg/app/ops/insightcollector.(*completedDeploymentDataCollector).Execute
    /home/runner/work/pipecd/pipecd/pkg/app/ops/insightcollector/deployment_collector.go:49
github.com/pipe-cd/pipecd/pkg/app/ops/insightcollector.(*Collector).Run.func2
    /home/runner/work/pipecd/pipecd/pkg/app/ops/insightcollector/collector.go:81
github.com/robfig/cron/v3.FuncJob.Run
    /home/runner/go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:136
github.com/robfig/cron/v3.(*Cron).startJob.func1
    /home/runner/go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:312

Pod: pipecd-ops-*

I've used kubectl exec to get into pipecd-ops- pod, then I installed Minio Client manually and configured S3 Object Storage, then I tried to list buckets, or create a dir inside the bucket, I have no problem to list bucket... , but Pod has error:

failed to stat minio object {"path": "insights/milestone.json", "error": "not found"}

How to reproduce it:

Environment:

• control-plane version: 0.43.1

Start at pkg/filestore/minio/minio.go:109 and pkg/insight/insightstore/milestonestore.go:30, then trace the call from pkg/app/ops/insightcollector/deployment_collector.go:49. Reproduce the scheduled insight collection with the reported object-storage setup and determine how the missing insights/milestone.json should be handled; done means the collector no longer reports an unexpected failure.