Open Source Go Browser Extensions and Plugins

Telegraf is an agent for collecting, processing, aggregating, and writing metrics. Design goals are to have a minimal memory footprint with a plugin system so that developers in the community can easily add support for collecting metrics. Telegraf is plugin-driven and has the concept of 4 distinct plugin types. Input Plugins collect metrics from the system, services, or 3rd party APIs. Processor Plugins transform, decorate, and/or filter metrics. Aggregator Plugins create aggregate metrics (e.g. mean, min, max, quantiles, etc.). Output Plugins write metrics to various destinations. New plugins are designed to be easy to contribute, pull requests are welcomed and we work to incorporate as many pull requests as possible. You can try Telegraf right in your browser in the Telegraf playground. Telegraf shares the same minimum requirements as Go.

Automate certificate management in cloud native environments. Cert-manager builds on top of Kubernetes, introducing certificate authorities and certificates as first-class resource types in the Kubernetes API. This makes it possible to provide 'certificates as a service' to developers working within your Kubernetes cluster. upport for popular CA types. Out of the box, cert-manager supports ACME (i.e. Let's Encrypt), HashiCorp Vault, Venafi, self signed and internal CA issuer types. cert-manager is Kubernetes native, and as such, it natively targets Kubernetes and OpenShift. This means it integrates well with other ecosystem tools and addons for your cluster, in order to seamlessly secure all your cloud native infrastructure.

This project is the source code of lightsailctl, a tool that augments Amazon Lightsail features in AWS CLI. lightsailctl is executed automatically by AWS CLI when certain subcommands are used, such as AWS lightsail push-container-image. lightsailctl is written in Go, so please install Go. Keep reading if you want to work with lightsailctl source code locally. This container image pushing logic requires a number of steps that are outsourced from AWS CLI to lightsailctl.

A Fluent Bit output plugin for Amazon Kinesis Data Firehose. This plugin will continue to be supported. However, we are pausing development on it and will focus on the high-performance version instead. If the features of the higher performance plugin are sufficient for your use cases, please use it. It can achieve higher throughput and will consume less CPU and memory. This plugin has been tested with Fluent Bit 1.2.0+. It may not work with older Fluent Bit versions. We recommend using the latest version of Fluent Bit as it will contain the newest features and bug fixes. We distribute a container image with Fluent Bit and these plugins.

A Fluent Bit output plugin for Amazon Kinesis Data Streams. A partition key is used to group data by shard within a stream. A Kinesis Data Stream uses the partition key that is associated with each data record to determine which shard a given data record belongs to. For example, if your logs come from Docker containers, you can use container_id as the partition key, and the logs will be grouped and stored on different shards depending upon the id of the container they were generated from. As the data within a shard are coarsely ordered, you will get all your logs from one container in one shard roughly in order. Nested partition key is supported and you can use -> to point to your target key which is nested under another key. For example, your partition_key could be kubernetes->pod_name. If you don't set a partition key or put an invalid one, a random key will be generated, and the logs will be directed to random shards.

A Fluent Bit output plugin for CloudWatch Logs. This plugin uses the AWS SDK Go, and uses its default credential provider chain. If you are using the plugin on Amazon EC2 or Amazon ECS or Amazon EKS, the plugin will use your EC2 instance role or ECS Task role permissions or EKS IAM Roles for Service Accounts for pods. The plugin can also retrieve credentials from a shared credentials file, or from the standard AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN environment variables. A template in the form of $(variable) can be set in log_group_name or log_stream_name. variable can be a map key name in the log message. To access sub-values in the map use the form $(variable['subkey']). Also, it can be replaced with special values to insert the tag, ECS metadata, or a random string in the name. It can achieve higher throughput and will consume less CPU and memory.

A Golang plugin collection for SublimeText 3, providing code completion and other IDE-like features. GoSublime is an IDE-like plugin for Sublime Text 3 mainly, but not limited to, providing integration for most of your Go/Golang development tools. Code completion from Gocode (fork). Context aware snippets via the code-completion popup. Sublime build system(ctrl+b) integrating with GoSublime 9o command prompt with live command output. lint/syntax check as you type or on save. Quickly jump to any linter error reported in any open file or package. Quickly fmt your source or automatically on save to conform with your coding standards. Easily create a new go file and run it without needing to save it first (9o replay), share your snippets (anything in the loaded file) on play.golang.org. List declarations in the current file or package; automatically add/remove package imports; quickly jump your import section(automatically goes to the last import).

This is a Helm plugin giving you a preview of what a helm upgrade would change. It basically generates a diff between the latest deployed version of a release and a helm upgrade --debug --dry-run. This can also be used to compare two revisions/versions of your helm release.

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS. Launch kubelet with network plugins set to cni (--network-plugin=cni), the cni directories configured (--cni-config-dir and --cni-bin-dir) and node ip set to the primary IPv4 address of the primary ENI for the instance (--node-ip=$(curl http://169.254.169.254/latest/meta-data/local-ipv4)). It is also recommended that you set --max-pods equal to (the number of ENIs for the instance type × (the number of IPs per ENI - 1)) + 2; for details, see vpc_ip_resource_limit.go. Setting --max-pods will prevent scheduling that exceeds the IP address resources available to the kubelet. The Amazon VPC CNI plugin for Kubernetes supports a number of configuration options, which are set through environment variables. The following environment variables are available, and all of them are optional.