Yoshiki Fujikane

This might happen because the resource key in the live resource differs from the resource used when pruning. - The actual resource key: `rbac.authorization.k8s.io/v1:ClusterRole:test:pod-reader` - The one used when pruning:...

As this PR https://github.com/pipe-cd/pipecd/pull/3991, all of the resources for the application belong to the namespace set on the `spec.input.namespace` in app.pipecd.yaml. So in PipeCD, the ClusterRole resource is also treated...

## Root cause: the resource key stored as livestate and the one on the annotation of actual k8s resource are different values, but actually, they are compared as if they...

Solution candidates The point is whether to fix or not as if they are equal. 1. fix not to compare them. (they are **not equal**) 2. fix to use of...

## Other stages ### Baseline load manifests in the same way with K8S_SYNC stage indirectly. (by using loadRunningManifests) https://github.com/pipe-cd/pipecd/blob/7b1103d027fcdbc2468af60deb5da758fcc8f6ae/pkg/app/piped/executor/kubernetes/baseline.go#L46 So the resourceKey is based on the k8s resource manifest, then...

📝 the namespace of the resourceKey is `spec.input.namespace` > `original namespace` https://github.com/pipe-cd/pipecd/blob/7b1103d027fcdbc2468af60deb5da758fcc8f6ae/pkg/app/piped/platformprovider/kubernetes/loader.go#L90-L91

There are two problems 1. We can't delete the cluster scoped resources if we set the namespace to the app.pipecd.yaml. - This is because the resource key stored as livestate...

📝 Prepared the issue for 2 https://github.com/pipe-cd/pipecd/issues/4861

Previous context: https://github.com/pipe-cd/pipecd/issues/4269#issuecomment-2031079364 After some investigations, I decided to fix the logic for the resource key as the ideal state. I think this problem is the incorrect namespace in the...

Hi @amye ! My name is Yoshiki Fujikane! I've been a maintainer for PipeCD since a month ago. https://github.com/cncf/foundation/pull/652 I would like to use cncf service desk. How can I...