Updates and recent posts about KubeLinter..

Posts
Description

Activity

@codechaintech started using tool Atlassian Bitbucket , 2 weeks, 1 day ago.

Link

@simme shared a link, 2 weeks, 1 day ago

Senior Engineering Manager, @canonical

Boring code is an organizational tell

Boring code is an organizational symptom, not an aesthetic failure. Co-change patterns in version control reveal team boundaries before any retrospective does; ownership concentration predicts defects better than code complexity metrics. With agents removing the friction that contained clever code accumulation, the incentive structures that produce boring code have never mattered more.

Activity

@simme started using tool Ubuntu , 2 weeks, 1 day ago.

Activity

@simme started using tool TypeScript , 2 weeks, 1 day ago.

Activity

@simme started using tool Python , 2 weeks, 1 day ago.

Activity

@simme started using tool PostgreSQL , 2 weeks, 1 day ago.

Activity

@simme started using tool lxd , 2 weeks, 1 day ago.

Activity

@simme started using tool Kubernetes , 2 weeks, 1 day ago.

Activity

@simme started using tool K6 , 2 weeks, 1 day ago.

Activity

@simme started using tool Juju , 2 weeks, 1 day ago.

KubeLinter, developed by StackRox (now part of Red Hat), is an open source linter that scans Kubernetes manifests and Helm charts to identify insecure configurations, deprecated patterns, and operational risks. It ships with a rich set of built-in checks covering security, reliability, and production readiness. Teams integrate KubeLinter into CI pipelines and GitOps workflows to enforce standards like non-root containers, proper resource limits, network policy requirements, and RBAC hygiene. Its speed, clarity, and simple rule-based design make it a valuable guardrail for Kubernetes platform teams and application developers aiming for secure, consistent deployments.