plone

ansible-collection-community-kubernetes-2.0.1-6.lbn36.noarch
Kubernetes Collection for Ansible. This collection has been deprecated in favor of ansible-collection-kubernetes-core. Users should change their collection names from `community.kubernetes.X` to `kubernetes.core.X` and replace this package with ansible-collection-kubernetes-core.
Located in LBN / … / DevOps / BastionLinux 36
ansible-collection-community-kubernetes-2.0.1-6.lbn36.noarch
Kubernetes Collection for Ansible. This collection has been deprecated in favor of ansible-collection-kubernetes-core. Users should change their collection names from `community.kubernetes.X` to `kubernetes.core.X` and replace this package with ansible-collection-kubernetes-core.
Located in LBN / … / DevOps / BastionLinux 36
ansible-collection-kubernetes-core-2.3.2-7.lbn36.noarch
ansible-collection-kubernetes-core provides the kubernetes.core (formerly known as community.kubernetes) Ansible collection. The collection includes a variety of Ansible content to help automate the management of applications in Kubernetes and OpenShift clusters, as well as the provisioning and maintenance of clusters themselves.
Located in LBN / … / DevOps / BastionLinux 36
argocd-cli-3.0.12-1.1.lbn36.x86_64
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. This packages contains the CLI to interact with the ArgoCD installation in a Kubernetes cluster.
Located in LBN / … / DevOps / BastionLinux 36
cockpit-kubernetes-0.106-1.lbn19.x86_64
The Cockpit components for visualizing and configuring a Kubernetes cluster. Installed on the Kubernetes master. This package is not yet complete.
Located in LBN / … / Core Linux / BastionLinux 19
cockpit-kubernetes-194-1.lbn25.x86_64
The Cockpit components for visualizing and configuring a Kubernetes cluster. Installed on the Kubernetes master. This package is not yet complete.
Located in LBN / … / Core Linux / BastionLinux 25
golang-github-terraform-providers-kubernetes-1.9.0-0.1.gitfc2b788.lbn25.x86_64
Terraform kubernetes provider
Located in LBN / … / Cloud Computing / BastionLinux 25
golang-github-terraform-provider-kubernetes-2.13.1-0.1.git9030924.lbn36.x86_64
Terraform kubernetes provider
Located in LBN / … / Cloud Computing / BastionLinux 36
grafana-loki-3.5.2-0.1.git257d2f6.lbn36.x86_64
Loki: like Prometheus, but for logs. Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream. Compared to other log aggregation systems, Loki: does not do full text indexing on logs. By storing compressed, unstructured logs and only indexing metadata, Loki is simpler to operate and cheaper to run. indexes and groups log streams using the same labels you’re already using with Prometheus, enabling you to seamlessly switch between metrics and logs using the same labels that you’re already using with Prometheus. is an especially good fit for storing Kubernetes Pod logs. Metadata such as Pod labels is automatically scraped and indexed. has native support in Grafana (needs Grafana v6.0). A Loki-based logging stack consists of 3 components: promtail is the agent, responsible for gathering logs and sending them to Loki. loki is the main server, responsible for storing logs and processing queries. Grafana for querying and displaying the logs. Loki is like Prometheus, but for logs: we prefer a multidimensional label-based approach to indexing, and want a single-binary, easy to operate system with no dependencies. Loki differs from Prometheus by focusing on logs instead of metrics, and delivering logs via push, instead of pull.
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-loki-3.5.2-0.1.git257d2f6.lbn36.x86_64
Loki: like Prometheus, but for logs. Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream. Compared to other log aggregation systems, Loki: does not do full text indexing on logs. By storing compressed, unstructured logs and only indexing metadata, Loki is simpler to operate and cheaper to run. indexes and groups log streams using the same labels you’re already using with Prometheus, enabling you to seamlessly switch between metrics and logs using the same labels that you’re already using with Prometheus. is an especially good fit for storing Kubernetes Pod logs. Metadata such as Pod labels is automatically scraped and indexed. has native support in Grafana (needs Grafana v6.0). A Loki-based logging stack consists of 3 components: promtail is the agent, responsible for gathering logs and sending them to Loki. loki is the main server, responsible for storing logs and processing queries. Grafana for querying and displaying the logs. Loki is like Prometheus, but for logs: we prefer a multidimensional label-based approach to indexing, and want a single-binary, easy to operate system with no dependencies. Loki differs from Prometheus by focusing on logs instead of metrics, and delivering logs via push, instead of pull.
Located in LBN / … / Core Linux / BastionLinux 36

Next 10 items » 1 2 3 4 5 6

Sections

Search results for kubernetes


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.