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
# install fish
$ brew install fish
https://medium.com/@ozbillwang |
A python code runs as text mode of https://chat.openai.com with model `gpt-3.5-turbo` via API | |
### Usage | |
1. install openai pythonpackage | |
``` | |
pip install openai python-dotenv | |
``` |
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
# install fish
$ brew install fish
#!/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] |
ssh-keygen -l -E md5 -f id_rsa
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": [
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
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: |
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:
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.
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