Search Results for "context"

kubie is an alternative to kubectx, kubens, and the k on prompt modification script. It offers context switching, namespace switching, and prompt modification in a way that makes each shell independent from others. It also has support for split configuration files, meaning it can load Kubernetes contexts from multiple files. You can configure the paths where Kubie will look for contexts, see the settings section. Kubie also has other nice features such as kubie exec which allows you to execute commands in a context and a namespace without having to spawn a shell and kubie lint which scans your k8s config files for issues and informs you of what they are.

Making SLOs with Prometheus manageable, accessible, and easy to use for everyone. When running Pyrra outside of Kubernetes, the SLO object can be provided through a YAML file read from the file system. For this, one container or binary needs to be started with the API argument and the reconciler with the filesystem argument. Here, Pyrra will save the generated recording rules to disk where they can be picked up by a Prometheus instance. While running Pyrra on its own works, there won't be...

...Instead of manually scanning logs for issues or relying solely on centralized monitoring stacks, LoggiFly proactively inspects streams of container output and notifies users through services like Ntfy, Slack, Discord, Telegram, or webhooks when significant events occur. It supports plain text, regex, and multi-line pattern matching, and its flexible alert templating lets operators tailor messages for clarity and context, including attaching relevant log excerpts. Beyond notifications, LoggiFly can take automated actions such as restarting or stopping containers when specific critical patterns are detected, which is especially useful for preventing damage from misbehaving services.

...Instead of buried changelogs, ideas and work items are represented as GitHub issues with labels that convey status, area, and priority. Customers watch, react, and comment directly on items, creating a transparent feedback loop between users and service teams. The issue history provides valuable context on trade-offs, design pivots, and integration plans across the container ecosystem on AWS. It is not a codebase; it is a living roadmap that signals what’s under consideration, in progress, or shipped. Teams use it to validate use cases, surface gaps, and coordinate previews with early adopters who can test features in realistic environments.

...It achieves this without the need for installing additional software on your workstation. Think of Geodesic as a containerized parallel to Vagrant, offering similar functionality within a Docker container context.

Lens is a Kubernetes IDE designed to simplify the management, monitoring, and troubleshooting of cloud-native applications. It provides a unified, context-aware graphical interface that allows developers and DevOps teams to interact with Kubernetes clusters more efficiently. Lens enables users to visualize workloads, inspect resources, and manage deployments without relying heavily on command-line tools. It supports multiple clusters simultaneously, making it easier to operate complex distributed environments. ...

Yet Another .NET Clean Architecture, but for a Microservices project. It uses Minimal Clean Architecture with DDD-lite, CQRS-lite, and just enough Cloud-native patterns applied on the simple eCommerce sample and run on Tye with Dapr extension.

...For e.g. enter 'kubectl get' and use up-arrow and down-arrow to browse through all kubectl get commands. You could also use CTRL+r to search from the history of commands. Details of the current context from kubeconfig is always readily displayed on the bottom toolbar. By pressing F4 button you can switch between the clusters and using F5 can switch between namespaces.