kubecost / cost-prediction-action Goto Github PK

Description:

Hello everyone, hope you're good.

In the project I'm trying to add this action, we use kustomize to avoid repeating the manifest configuration between different environments.

We have added a step to build the manifests, according to kustomize and input this result into the kubecost action.

But we're having a problem with some custom operators, for example:

2023-05-03T14:38:49.339005414Z FTL Failed to run: parsing file bytes as K8s specs: walking overlays/compiled to find K8s objects: reading overlays/compiled/xxx-out.yml as file with specs: converting specs to bytes: decoding: no kind "SecretProviderClass" is registered for version "secrets-store.csi.x-k8s.io/v1alpha1" in scheme "pkg/runtime/scheme.go:100"

As you can see, it's throwing an error due to the SecretProviderClass configuration.

It would be nice to let us explicitly add a filter to this action, so it can ignore some manifests, while taking into consideration the other ones.

Kubeconform for example, has a flag, so we can explicitly define what are the objects to skip.

In our current environment, we use a centralized argo repository to maintain all our kubernetes manifests.
If we were to scan all the corresponding directories, it would produce too much information for us to reliably digest.

My proposal is to extend the current solution to support scans of the git diff information for new or modified manifests and calculate the new cost of added or modified manifests for the entire repository vs the current directories input.