The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...

The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.

RPM resource kube-no-trouble

Easily check your cluster for use of deprecated APIs Kubernetes 1.16 is slowly starting to roll out, not only across various managed Kubernetes offerings, and with that come a lot of API deprecations1. Kube No Trouble (kubent) is a simple tool to check whether you're using any of these API versions in your cluster and therefore should upgrade your workloads first, before upgrading your Kubernetes cluster. This tool will be able to detect deprecated APIs depending on how you deploy your resources, as we need the original manifest to be stored somewhere. In particular following tools are supported: * file - local manifests in YAML or JSON * kubectl - uses the kubectl.kubernetes.io/last-applied-configuration annotation * Helm v2 - uses Tiller manifests stored in K8s Secrets or ConfigMaps * Helm v3 - uses Helm manifests stored as Secrets or ConfigMaps directly in individual namespaces

Found 1 sites for kube-no-trouble

• https://github.com/doitintl/kube-no-trouble

Found 8 RPM for kube-no-trouble

Generated by rpm2html 1.6

Fabrice Bellet