ckotzbauer / chekr Goto Github PK

• Add current requests and limits
• Restructure columns

/kind feature
/kind cleanup

• Publish channels (Snap, ...)
• Signing with Cosign (Artifacts, Image)

Use the current Kubernetes server-version as default value for --k8s-version
/kind feature

• CronJob(s) which are generating given reports with the chekr-cli at a time.
• Built-in NGINX to serve generated reports.

/kind feature

Now, all pods are displayed with the "resources" subcommand which where selected through various flags.
It should be possible to only emit pod-data for pods which have usage-data far away from its requests or limits.
Suggestion:

• New int-flag: --limits-threshold e.g. --limits-threshold 20
• New int-flag: --requests-threshold e.g. --requests-threshold 30

When one of these flags is present, only pods are shown which have a greater or less resource utilisation in average compared to the 100% values of its limits or requests (depending on the flag).

--limits-threshold 20 for example will only show pods which have an average utilisation from less 80% or greater than 120% compared to the pod-limits.

/cc @devRoemer
/kind feature

/kind documentation

Add --kubeconfig parameter to specify file-location manually.
/kind feature

This issue provides visibility into Renovate updates and their statuses. Learn more

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• deps: update module k8s.io/client-go to v12

• Check this box to trigger a request for Renovate to run again on this repository

/kind feature

They do not have current usages and the analysis will fail.
/kind bug

/kind bug

Programmatically add a short-lived port-forward to use Pod-URLs to query from. If a URL with one of the following formats is detected, it is considered as "in-cluster":
namespace/podname:port

/kind feature

Currently 30 days are queried hard-coded from Prometheus for the analysis. Add a paramter
/kind feature

Add parameter to specify the Prometheus metric used.
/kind feature

Exit with a non-zero exit-code by default if deprecations were found. Add a cli-option to omit this behavior.
/kind feature

I'm trying to use chekr with AKS Clusters which results in the following error message:

FATA[0000] Could not create Kubernetes client from config! error="no Auth Provider found for name \"azure\""

Is there a way to get this to work with the current version?

This is the user configuration generated by azurecli:

users:
- name: a-user
  user:
    auth-provider:
      config:
        apiserver-id: 00000000-0000-0000-0000-000000000000
        client-id: 00000000-0000-0000-0000-000000000000
        config-mode: "1"
        environment: AzurePublicCloud
        tenant-id: 00000000-0000-0000-0000-000000000000
      name: azure

• CLI-Arguments
• Configuration-YAML
• Environment-Variables
• ConfigMap stored in Kubernetes

(Applied in order => CLI wins)

/kind feature

https://github.com/kubernetes-sigs/wg-policy-prototypes
/kind feature

• Move chekr deprecation command to chekr deprecation list

• Move --omit-exit-code and --throttle-burst flags to chekr deprecation list

• Create subcommand chekr deprecation kyverno-create

  This subcommand generates and applies Kyverno Policies as specified by the flags. If --dry-run and --output is given, the rules will only be generated. All existing rules generated by chekr will be replaced.

  • Parent flags --ignored-kinds and --k8s-version are respected.
  • New flag: --validation-failure-action {audit|enforce} (default audit)
  • New flag: --background {true|false} (default true)
  • New flag: --category string (default tbd.)
  • New flag: --subject string (default tbd.)
  • New flag: --output {json|yaml}
  • New flag: --dry-run {true|false}

• Create subcommand chekr deprecation kyverno-remove

  This subcommand removes all Policies created by chekr.

/kind feature