Search Results for "cluster"

...The Jaeger Operator can be installed in Kubernetes-based clusters and is able to watch for new Jaeger custom resources (CR) in specific namespaces, or across the entire cluster. There is typically only one Jaeger Operator per cluster, but there might be at most one Jaeger Operator per namespace in multi-tenant scenarios.

Deploy Kubernetes Helm Charts. Declaratively deploy your Kubernetes manifests, Customize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD. Keep a directory of chart value files and maintain changes in version control. Apply CI/CD to configuration changes. Periodically sync to avoid skew in environments.

kube-bench is a tool that checks whether Kubernetes is deployed securely by running the checks documented in the CIS Kubernetes Benchmark. Trivy, the all-in-one cloud-native security scanner, can be deployed as a Kubernetes Operator inside a cluster. Both, the Trivy CLI, and the Trivy Operator support CIS Kubernetes Benchmark scanning among several other features. There are multiple ways to run kube-bench. You can run kube-bench inside a pod, but it will need access to the host's PID namespace in order to check the running processes, as well as access to some directories on the host where config files and other files are stored.

Knative Serving defines a set of objects as Kubernetes Custom Resource Definitions (CRDs). These resources are used to define and control how your serverless workload behaves on the cluster. The service.serving.knative.dev resource automatically manages the whole lifecycle of your workload. It controls the creation of other objects to ensure that your app has a route, a configuration, and a new revision for each update of the service. Service can be defined to always route traffic to the latest revision or to a pinned revision. ...

...Originally used to selectively roll out changes to the SourceForge site, the library lets you easily control whether a particular change (a switch) is active. You can make switches active for a certain percentage of visitors, all visitors to a particular host in a cluster, or if a particular string is present in the query string. Furthermore you can easily create your own conditions to do fancier things like geo-targeting, specific users, etc. In short, Switchboard turns you into a continuous deployment ninja.

The Orchestrator server is responsible for distribution and launch of simple apply/rollback shell scripts in a particular order across multiple servers . If for any reason deployment is failing at a particular stage the process will stop and you can rollback any changes done until then. In case you want to deploy your code or just call your preferred DSC client to apply the configuration locally the Orchestrator can be a handy tool. The operation can be started manually or scheduled,...