service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval
(in minutes)service.beta.kubernetes.io/aws-load-balancer-access-log-enabled
(true|false)service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix
service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags
(comma-separated list of key=value)service.beta.kubernetes.io/aws-load-balancer-backend-protocol
(http|https|ssl|tcp)service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled
(true|false)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#! /bin/bash | |
# Sass: http://sass-lang.com/ | |
# Sass is a "smart" form of css, supporting nested targeting of html, variables and logic | |
# scss is a variant of sass using a syntax much closer to css | |
# Compass: http://compass-style.org/ | |
# Compass is a sass framework containing a range of shortcuts for cross-browser css effects. | |
# rounded corners, transparency... |
The easiest way to create and update a docker-registry secret in Rancher 2.x for an AWS ECR repo is to set up a CRON job that uses the AWS CLI and Kubectl.
- Log into the host machine where the cluster is running
- Install AWS CLI and configure it to use an IAM role that can read the ECR credentials.
- Test the CLI config using this command:
aws ecr --region <your_ecr's_region> get-login-password
- Install kubectl and configure it with the yaml for the cluster in which you want to define the secret
- Create a shell script like this:
# Delete the secret if it already exists (there is no way to update it)