Yoshiki Fujikane
Yoshiki Fujikane
**What would you like to be added**: This issue tracks the progress for deprecating Platform Provider and Kind toward piped plugin architecture in pipedv1. The purpose is to manage application...
**What this PR does / why we need it**: I fixed to finish executing the SCRIPT_RUN_ROLLBACK stage successfully when the pipeline has multiple SCRIPT_RUN stages. Currently, the SCRIPT_RUN_ROLLBACK stage is...
**What happened**: When changing the namespace, the workload remains in the old namespace.  **before** ``` % kubectl get deployment -n test simple-hoge NAME READY UP-TO-DATE AVAILABLE AGE simple-hoge...
**What would you like to be added**: We want to show the Sync status for the application managed by pipedv1 (for plugin architecture). **features** - show sync status icon by...
**What would you like to be added**: We want to show the Livestate for the application managed by pipedv1 (for plugin architecture). Especially showing the Livestate for each deploy target....
**What would you like to be added**: This issue is the meta (epic) issue for the livestate feature in plugin architecture. TODO - [x] make RFC - [x] define an...
**What happened**: When updating the version of the base image `piped-base` in piped-base-okd, failed to build the image on my local machine. I can build the image with the current...
**What would you like to be added**: We want to support the plan preview with the diff between actual resources and target manifests, discussed in https://github.com/pipe-cd/pipecd/pull/5986 > At first, we...
**What happened**: Custom resources that support multiple API versions may not be pruned. Here is the example External Secrets (helm chart: v0.16.1) This version supports both v1beta1 and v1 as...
### What happened? When executing kustomize build including the karpenter 1.1.0 Helm chart (https://github.com/aws/karpenter-provider-aws/tree/v1.1.0/charts/karpenter-crd), an error occurred, causing the build to fail. This Helm chart does not include a values.yaml....