Search Results for "using"

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. ...

kubectl tree is a kubectl plugin that lets you visualize Kubernetes object hierarchies as a tree by following the ownerReferences set on API objects. Instead of manually chasing which ReplicaSet owns which Pods or which higher-level controller is responsible for a given resource, it prints an ASCII tree that shows parent-child relationships at a glance. This is especially useful for understanding how complex workloads like Deployments, StatefulSets, Knative Services, or Agones Fleets fan out...

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. ...

...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.