ozbillwang

Why use fish for kubernetes autocompletion

I am stucking on kubernetes autocompletion on my macbook for a while. Whatever I try with the document (https://kubernetes.io/docs/tasks/tools/install-kubectl/#enabling-shell-autocompletion) it does not work

Enable kubernetes automation in fish is the simplest solution

# install fish
$ brew install fish

ozbillwang

#!/usr/bin/env bash
#
# RKIND is a naive helper script to start KIND and Rancher Management Server
#

set -u
set -o pipefail

RANCHER_CONTAINER_NAME="rancher-for-kind"
RANCHER_HTTP_HOST_PORT=$[$[RANDOM%9000]+30000]

ozbillwang

ssh-keygen -l -E md5 -f id_rsa

ozbillwang

The problem

The document quality of Google Cloud is far away if compare with AWS. Here is a sample.

If you met below error, when running packer or other SDK,

$ cat packer.json
{
 "builders": [

ozbillwang

There are several ways to clone a repository from github. Similar from other providers, such as bitbucket, gitlab, etc.

https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols

Mostly, we use

• http
• ssh

Sample clone commands:

ozbillwang

AWSTemplateFormatVersion: 2010-09-09
Description: 'Registers ecs tasks to a second target group'
Parameters:
  ClusterArn:
    Description: 'ANR of cluster the service resides in'
    Type: String
  ServiceName:
    Description: 'Name of the service to register'
    Type: String
  ContainerName:

ozbillwang

Unfortunately as of writing this (Oct 18, 2017) there is no built in integration for multiple target groups per AWS ECS service. Here are a few things you can try:

1. If your application just serves port 80 (HTTP) & port 443 (HTTPS) then you should consider using the application load balancer and terminating SSL at the load balancer. This will allow your application to function using just port 80.

2. If your application serves different ports that are backed by different components, perhaps speaking different protocols then you should consider splitting the application into multiple ECS services. This has the benefit of allowing the different components to independently scale

ozbillwang

https://stackoverflow.com/questions/48460316/terraform-take-parameter-name-from-variable

According to this comment, dynamic variable names are not possible at this time in HCL.

You can use zipmap to emulate this, though it's a bit of a clunky workaround;

locals {
  ec2_tag_keys = ["Name", "Group", "${var.vault_tag_name}"]
 ec2_tag_vals = ["${var.name}", "${var.group_tag}", "${var.vault_tag_value}"]

ozbillwang

# filter by request host header
varnishlog -q 'ReqHeader ~ "Host: example.com"'

# filter by request url
varnishlog -q 'ReqURL ~ "^/some/path/"'

# filter by client ip (behind reverse proxy)
varnishlog -q 'ReqHeader ~ "X-Real-IP: .*123.123.123.123"'

# filter by request host header and show request url and referrer header

ozbillwang

Sometime, you can't wait and try new features in serverless framework (github.com/serverless/serverless)

serverless/serverless#4325 (comment)

run below commands, this build will generate new serverless command.

cd <serverless_repo_full_path>
# Fake the environment "SENTRY_DSN", otherwise, it will stop the build
export SENTRY_DSN=demo