With help from: https://devopscube.com/setup-kubernetes-cluster-kubeadm/
Vagrant.configure("2") do |config|
config.vm.provision "shell", inline: <<-SHELL
VERSION="1.29"
KUBERNETES_VERSION="$VERSION.2-1.1"
# create topic | |
# docker exec -it kafka bash -c "kafka-topics.sh --create --topic hello-topic --bootstrap-server localhost:9092 --partitions 1 --replication-factor 1" | |
# create consumer (with group, blocks on stdout) | |
# docker exec -it kafka bash -c "kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic hello-topic --group hello-group --from-beginning" | |
# create producer (one message via stdin) | |
# docker exec -it kafka bash -c "echo "test" | kafka-console-producer.sh --bootstrap-server localhost:9092 --topic hello-topic" | |
services: |
With help from: https://devopscube.com/setup-kubernetes-cluster-kubeadm/
Vagrant.configure("2") do |config|
config.vm.provision "shell", inline: <<-SHELL
VERSION="1.29"
KUBERNETES_VERSION="$VERSION.2-1.1"
STACK_BASE_NAME=sko-demo
VCPRegion=US # EU does not fully support K8s cluster ... yet!
VCPAPIKey=??? # value from https://container-gulch.venafi.cloud/platform-settings/user-preferences?key=api-keys
export AWS_PROFILE=venafi-se # assuming aws credentials have been set up for this account
aws cloudformation create-stack \
--stack-name ${STACK_BASE_NAME}-$(date +"%y%m%d%H%M%s") \
--template-url https://venafi-ecosystem.s3.amazonaws.com/tlspk/v2/cfn-tlspk-cluster-bootstrapper.yaml \
Solution tested with MacOS client.
Note: The EC2 instance created by this CloudFormation template is pre-configured to provide the following:
An example based upon documentation here
This code has been tested on x86 Ubuntu
These instructions aim to simplify those already laid out here.
The following assumes your AWS CLI has been pre-authenticated with an AWS account.
stack_id=$( \
aws cloudformation create-stack \
--stack-name ubuntu-docker-firefly \
Assuming we have cert-chain and private key files extracted from TLSPC via DigiCert (let's call them my-cert.chain
and my-cert.key
),
how do we get them prepared for AWS ACM import.
In this case my-cert.chain
is a full chain and my-cert.key
is an encrypted private key.
As such we need to cope with two requirements: