feat: Allow custom column configurations for resource views (similar to K9s)

[mreparaz]

What problem are you trying to solve?

Currently, sofka uses a generic rendering pipeline with hardcoded/built-in columns for standard Kubernetes resources, and falls back to a basic NAME and AGE layout for missing or custom resources (CRDs). Unlike K9s, there is no native way for a user to customize which columns are displayed, their alignment, or how JSON/Go templates parse specific fields into a custom table view.

Proposed solution

I would love to see a configuration mechanism (such as a views.yaml or a dedicated section in the sofka config file) that lets users override or define custom columns for any Kubernetes resource or CRD.
Ideally, it could look something like this:

• Ability to map custom headers to specific JSON path expressions (e.g., .status.podIP, .spec.replicas).
• Options to set column properties like width, alignment, or visibility toggles.
• A fallback mechanism where sofka still uses its excellent defaults if no custom view is provided.

Alternatives considered

Using kubectl get -o custom-columns=... or switching back to k9s for debugging complex CRDs that require seeing custom status fields immediately on the dashboard.

Additional context

No response

[nklmilojevic]

Thanks for describing the use case. Custom columns are already supported in the current code through the views section in the config file. See the custom view documentation.

You can select fields with JSON Pointer paths such as /status/podIP or /spec/replicas, set column width and alignment, and use wide = true to show a column only in wide mode. Custom columns can extend or replace the default columns. sofka also supports CRD printer columns and a Kubernetes Table API fallback.

The field syntax is JSON Pointer, rather than JSONPath or Go templates. Separate visibility controls for each column are not covered by wide mode.

Which sofka version are you using? Could you share a resource or CRD example and the columns you want to display? That will help us check whether the existing configuration meets your needs or whether a specific change is needed.