#announcements - September 2018

320 messages

This channel is for workspace-wide communication and announcements. All members are in this channel.
Archive: https://archive.sweetops.com

September 2018
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
There shouldn’t be anything necessary to add. I believe @Daren and and @Max Moon haven’t had problems with this.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
(Note that annotation is for the commercial edition which does not apply to you)
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
“Support for websockets is provided by NGINX out of the box. No special configuration required.”
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
So I guess what I mean to say is just configure the ingress as you would any other service.
Jeremy G (Cloud Posse)
Jeremy G (Cloud Posse)about 8 years ago
Thanks. I know ELB doesn't support Websocket stickiness and I forgot we're already using nginx.
Jeff
Jeffabout 8 years ago
For cloudposse/terraform-aws-rds-cluster... does anyone know why it won't let me assign the value of a var for admin_password?
Jeff
Jeffabout 8 years ago
I get the following error...
Jeff
Jeffabout 8 years ago
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
i’ll check @Jeff
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
just created a cluster with the following config
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
module "rds_cluster_aurora_postgres" {
  source             = "git::<https://github.com/cloudposse/terraform-aws-rds-cluster.git?ref=master>"
  name               = "postgres"
  engine             = "aurora-postgresql"
  cluster_family     = "aurora-postgresql9.6"
  cluster_size       = "2"
  namespace          = "eg"
  stage              = "dev"
  admin_user         = "admin1"
  admin_password     = "Test123456789"
  db_name            = "dbname"
  instance_type      = "db.r4.large"
  vpc_id             = "vpc-XXXXXXXX"
  availability_zones = ["us-east-1a", "us-east-1b"]
  security_groups    = []
  subnets            = ["subnet-XXXXXXXX", "subnet-XXXXXXXX"]
  zone_id            = "ZXXXXXXXXXXXX"
}
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
output "name" {
  value       = "${module.rds_cluster_aurora_postgres.name}"
  description = "Database name"
}

output "user" {
  value       = "${module.rds_cluster_aurora_postgres.user}"
  description = "Username for the master DB user"
}

output "password" {
  value       = "${module.rds_cluster_aurora_postgres.password}"
  description = "Password for the master DB user"
}

output "cluster_name" {
  value       = "${module.rds_cluster_aurora_postgres.cluster_name}"
  description = "Cluster Identifier"
}

output "master_host" {
  value       = "${module.rds_cluster_aurora_postgres.master_host}"
  description = "DB Master hostname"
}

output "replicas_host" {
  value       = "${module.rds_cluster_aurora_postgres.replicas_host}"
  description = "Replicas hostname"
}
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Outputs:

cluster_name = eg-dev-postgres
master_host = <http://master.postgres.XXXXXXXXX.net|master.postgres.XXXXXXXXX.net>
name = dbname
password = Test123456789
replicas_host = <http://replicas.postgres.XXXXXXXX.net|replicas.postgres.XXXXXXXX.net>
user = admin1
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@Jeff not sure why you have the error
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Is there an enabled flag?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Enabled by default
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Ok, and what happens when you set to false? :)
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Nothing gets provisioned
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
As we already do in terraform-root-modules
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Ok
U
Unknown Userabout 8 years ago
There is 1 event this week
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
Actually it will be at 11 am pst

Unfortunately, I have a conflict at 11am PST this time. I’m going to stick with 9:00 am. We’ll schedule the next one at 11am which was the most popular time according to the poll.
Toby
Tobyabout 8 years ago
Hi Gang,

I’ve just started using your vpc_peering terraform module and have run into an issue during the plan stage.
I’m getting

* module.vpc_peering.data.aws_route_table.requestor: data.aws_route_table.requestor: value of 'count' cannot be computed


I checked out the FAQ at
https://github.com/cloudposse/docs/blob/master/content/faq/terraform-value-of-count-cannot-be-computed.md
and it doesn’t seem to be the same issue.

I am getting it during the plan stage when the requestor_vpc_id is coming from the output of a vpc module, however that vpc hasn’t yet been created and the id is going to be computed at this stage.

Something you’ve seen before and if so is this a supported scenario? Can provide more info if needed.
Toby
Tobyabout 8 years ago

module "vpc" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "1.40.0"

  name = "hub-vpc"
  cidr = "${var.bit_mask_16}.0.0/16"
  azs             = ["${var.az_a}"]
  private_subnets = ["${var.bit_mask_16}.1.0/24"]
  public_subnets  = ["${var.bit_mask_16}.101.0/24"]

  enable_nat_gateway = true
  enable_vpn_gateway = false

  tags = {
    Terraform = "true"
    Environment = "hub"
  }
}

module "vpc_peering" {
  source           = "git::<https://github.com/cloudposse/terraform-aws-vpc-peering.git?ref=master>"
  namespace        = "hub"
  stage            = "dev"
  name             = "hub-to-mc"
  requestor_vpc_id = "${module.vpc.vpc_id}"
  acceptor_vpc_id  = "${var.mc_vpc_id}"

  tags = {
    Terraform = "true"
    Environment = "hub"
  }
}

Toby
Tobyabout 8 years ago
"${var.mc_vpc_id}" is a hard coded id of an existing vpc in the same account.
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
hi @Toby I’ll get to your question soon (we’ve seen that too)
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
let’s move the conversation to #terraform
Toby
Tobyabout 8 years ago
Thanks. Want me to link or copy/paste there?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
yes please
Toby
Tobyabout 8 years ago
np
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@Jeff what’s your status on terraform-aws-rds-cluster?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
let’s move to #terraform as well
Jeff
Jeffabout 8 years ago
@Andriy Knysh (Cloud Posse) I wasn't able to get admin_password to take a variable. I ended up using sed.
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
we improved the examples for the module, did you try this https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/examples/basic/main.tf ?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
was tested as it is and was working
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@Jeff ^
siert
siertabout 8 years ago
I saw that the terraform-rds-cluster module supports DNS friendly names for both master and replica’s. This may cause issues when SSL connections to the database are being used. Perhaps, it’s wise to document this somewhere? And according to the markdown, the zone id is required - which seems a bit odd to me.
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@siert thanks, if you want the zone to be optional (and I see why), please open an issue in the repo and we’ll implement it
U
Unknown Userabout 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
antonbabenko
antonbabenkoabout 8 years ago
Awesome chat! Thanks everyone for inputs!
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
thanks guys! @antonbabenko great talking points. will summarize what I remember. 😃
antonbabenko
antonbabenkoabout 8 years ago
What you will be missing I will try to reflect in my work document 🙂
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Just don't summarize my last sentence, that was quite unsummarizable.
jonas haskins
jonas haskinsabout 8 years ago
Hey friends, trying to lock down to a specific CP release of terraform-aws-rds-cluster?
jonas haskins
jonas haskinsabout 8 years ago
having issues where i can build a db, which works fine, and then if i simply run the same tf code again, instead of saying ' no changes' it rips it down and rebuilds : (
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
hi @jonas haskins
jonas haskins
jonas haskinsabout 8 years ago
hello !
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
let’s move to #terraform
jonas haskins
jonas haskinsabout 8 years ago
ok
antonbabenko
antonbabenkoabout 8 years ago
https://nanobrain.io/ - give it a try if you have strange bug you don’t even know where to look into. I tried it on Terraform errors during apply and it gave me some tips (I knew them very well before, because I could search on github, but still)
Gonzalo Peci
Gonzalo Peciabout 8 years ago(edited)
Any of you guys configuring your services through SSM/ETCD/etc dynamically (automatically updating after run). There are several examples online of using somthing like confd or similar to dynamically update your service from some K/V store, I was thinking of the failure domain for this scenarios because lets say someone/something updates a k/v for that service, the service reloads and fails now (all containers, since it has no way of green/blue) now your entire service is down. I have not seen any blog/article talk about this either, but it seems really risky.

thoughts?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Yes, I have used etcd/confd in the past. Any system that automatically reloads all services when the value changes is inherently fragile. That’s why the kubernetes approach is the best we can do: update secrets or configmaps, then trigger rolling updates which will abort if health checks fail.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
We use chamber, but it does not automatically reload. So it is compatible with the rolling update strategy.
Justin King
Justin Kingabout 8 years ago(edited)
I personally swear by SSM/Consul KV stores (not tried etcd). Couple of thoughts there:

1. there is no reason your configs shouldn't be subject to the same dev/test/prod flow that everything else is. Keep your SSM config in cloudformation/teraform/ansible/whatever all codified with a deployment pipeline. If a bad setting crashes in test it never makes it into prod. It also means during development it's super easy to replicate running configs if needed, as well as better unit test potential as you have "real world configs" you can test containers/functions against.
2. for more dynamic settings (that maybe an ops team is applying to a live system to tune things), simply don't grant direct access to the KV. Instead there should be an api abstraction so your devs can "protect" fields from getting bad settings. Ops don't really know the ugly details of that var after all, so wrap it up to prevent the unpredictable "oops i used a string instead of a list" drama.
3. SSM is inherently region based. If you blue/green across regions settings don't "spill". Consul has a "datacenter" concept which works similarly but is a bit more flexible because it's not a baked in service. Both also have version history so it's easy to undo a bad change ... and sometimes I've even seen companies nest versions into the kv/path, though that's not something I've personally done.
4. It's just a good idea to keep your configs separate from code. This fits very naturally into that paradigm, and I'm not rebuilding code just because I want to change a minor setting.
5. KV stores don't automatically reload anything. That's up to the dev and how he wrote his code. If he only polls the setting on boot then you have to restart the containers. Lambdas obviously will poll every run because of their nature. The fragility of the services is in the hands of the devs at the end of the day, or confd/consul-template if you automated that ... but honestly that's still you making the stability decision.
Justin King
Justin Kingabout 8 years ago
the best real-world example I could point to would be Amazons RDS service. I'm sure you noticed but every run-time configurable setting is stored in SSM for those database servers.
Justin King
Justin Kingabout 8 years ago
I'd also add it's inevitable if you go serverless, which is honestly how I learned to love it. I was forced to take the journey then on the end of it I went "huh, why didn't I do this sooner"?
Gonzalo Peci
Gonzalo Peciabout 8 years ago
I know KV stores dont automatically reload everything, much to the contrary I saw many people advocating/writing/blogs/etc about auto reload, and I was concerned about how they handled failure domains
Gonzalo Peci
Gonzalo Peciabout 8 years ago
tbh we only use KV for secrets, and I think they are a good usecase for dynamic values created from other services but not for the core settings of the service itself.
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Hi @Gonzalo Peci What kind of dynamic values would see as a possible fit ? And what about SSM rate limiting ?
Gonzalo Peci
Gonzalo Peciabout 8 years ago
No particularly in SSM, I was thinking more about Consul/etcd/etc
Gonzalo Peci
Gonzalo Peciabout 8 years ago
something like Service A uses some details from Service B, service B keeps them up to date when running, but Service A still runs without those
Gonzalo Peci
Gonzalo Peciabout 8 years ago
like how you do service discovery
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
What would be the advantage of this over using json http endpoints, as in the way microservices would normally talk to each other. I'd like to understand.
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
With this I mean, if service A needs some of those params from B, A would connect to B's json endpoint, retrieves params, and service A stores it in redis with some expiry information.
Gonzalo Peci
Gonzalo Peciabout 8 years ago(edited)
Im not saying it is better. Its a different way I guess. Just to clarify, im not talking about using it to do queries through Consul, mostly discovering parameters of the other services or similar
Gonzalo Peci
Gonzalo Peciabout 8 years ago
in a mesh/service discovery pattern, you will query a KV store like consul/etcd to get the ips/ports of ServiceB and then route to them (be it through itsio/etc or directly from your service A) but I have seen many patterns where people also store Service config or dynamic service options for other services in the KV.
Gonzalo Peci
Gonzalo Peciabout 8 years ago
another example of what I was talking about: https://github.com/breser/git2consul
U
Unknown Userabout 8 years ago
There are no events this week
Justin King
Justin Kingabout 8 years ago
Redis and Consul aren't really designed to solve the same problems though. Heck you can find blogs of people using one to help configure the other:
https://www.joyent.com/blog/redis-on-autopilot
Gonzalo Peci
Gonzalo Peciabout 8 years ago
is this related to my comments? as I never mentioned redis
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Can someone advise me good literature on implementing "Continuous Delivery", preferably something readable for non-devops ?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Hrmmm so are you looking for something that sells the merits of Continuous Delivery for non techies? E.g. why we should practice it rather than how to do it with some specific technologies
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago(edited)
Correct.. I found two articles which look helpful. Docker Orchestration is nice and all but the goal is to boost development. I'm currently helping a company which has not really implemented CI let alone CD, and a lot of manual QA..

https://harness.io/2018/04/10-signs-you-dont-do-continuous-delivery/ &
https://semaphoreci.com/blog/2017/07/27/what-is-the-difference-between-continuous-integration-continuous-deployment-and-continuous-delivery.html
loren
lorenabout 8 years ago
if you find a resource that convinces this company, i'd love to hear about it 😄
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago(edited)
Well.. these were already a good start it seems, so they want to start with the lesser important services first.
Challenge is that this works with good test coverage. So I stressed the importance that they start writing proper tests for their new features or this idea will fail and it will go back to manual QA with 2 weekly press on the button releases 🤪
Justin King
Justin Kingabout 8 years ago
@Gonzalo Peci sorry about that minor derail, @Maarten van der Hoef mentioned redis so I was trying to keep both going in one reply. I clearly failed 🙂
Eric Garza
Eric Garzaabout 8 years ago
Hello, I'm new here, any chance we can add custom_error_response = ["${var.custom_error_response}"] to the https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn module? I have not really contributed to github projects before and thought I'd ask here. Could I use the non S3 cdn module with an existing S3 origen?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@Eric Garza hello
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
let’s move this conversation to #terraform
ff
ffabout 8 years ago
Hi, just stumbled here by accident. Interesting stuff. Reading into it 👋
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
hi @ff, welcome to the community
antonbabenko
antonbabenkoabout 8 years ago
Hi @ff! Most of us are here by accident, so welcome to the club 🙂
ff
ffabout 8 years ago
amazing stuff to explore. more night shifts to come 😄
GC
GCabout 8 years ago
Hello everyone
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
welcome @GC @ff!
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
not a bad place to stumble into
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
what are you guys working on?
Jamie Nelson (BitFlight)
Jamie Nelson (BitFlight)about 8 years ago
I miss you guys.
Jamie Nelson (BitFlight)
Jamie Nelson (BitFlight)about 8 years ago
I’m doing long days at the moment but I remember our time together fondly
sarkis
sarkisabout 8 years ago
not sure if you all saw this yet 😞 https://justi.cz/security/2018/09/13/alpine-apk-rce.html
OGProgrammer
OGProgrammerabout 8 years ago
I know a few security companies that won't use alpine for compatibility reasons but that's not good.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Heh, and we just discovered it doesn’t use TLS by default on repos
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Ryan Smith
Ryan Smithabout 8 years ago
Write everything in Go and use FROM scratch Docker containers in Multi-Stage builds. Problem solved 😉
Mark Johnson
Mark Johnsonabout 8 years ago
Morning. Is this the cloudposse general slack hangout?
Mark Johnson
Mark Johnsonabout 8 years ago(edited)
Setting up a new multi-account setup in aws for small/medium company (not large) .. In the following scenario ... would there be any reason to NOT have IAM users in the root account


[Root]                  (Consolidated Billing / Org Root +  IAM users here)
[Security]              (Central logs, audits)
[Prod], [Dev], [Local]  (Environment application specific accounts)

or


[Root]                  (Consolidated Billing / Org Root)
[Security]              (Central logs, audits)
[Identity]              (IAM here?)
[Prod], [Dev], [Local]  (Environment application specific accounts)

So to clarify -- are there advantages having a separate Identity / Hub / Gateway account for IAM? or since it's a somewhat smaller deployment ... can I just store IAM in ROOT account? I've seen setups both ways .. but looking for a reason FOR or AGAINST
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
currently we have IAM users/roles in the root account, but we’ve been discussing to move it to a new identity account
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
the reason might be that nobody should access the root (billing) account
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
and also, in some companies they don’t even allow to do it
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
but for a small setup, both ways should work, depends on if you want to give access to the billing account to somebody who needs to manage IAM
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@Erik Osterman (Cloud Posse) has more insights into this
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
but in general, yes, having a separate identity is more secure and will work for more companies/use-cases
Mark Johnson
Mark Johnsonabout 8 years ago
Yeah my thoughts similarly ... the only thing I could think of if somehow the IAM users are misconfigured could give potentially elevated priv in root account ; while they could be misconfigured in the identity as well .. but slightly harder to cross-account jump into root to elevate
OGProgrammer
OGProgrammerabout 8 years ago
I'm very determined to fix the elasticbeanstalk terraform provider , I miss it saying "nothing changed" haha... Any helpful links for doing Go/Terraform development?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
@OGProgrammer thanks, finally somebody would fix that 🙂
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago(edited)
we think the problem is that TF has one set of params while EB maintains a diff (smaller) set of params (relevant to your env)
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
if the assumption is correct, then what needs to be done is to determine the diff b/w only those params that EB returns from the API (not all params that TF has in the module)
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
although it could be more complicated than that
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
antonbabenko
antonbabenkoabout 8 years ago
Wow, gitter room for Terraform is so active. It is nice to see so many familiar faces there 🙂 Notifications in gitter are weird, I have just received notifications from people who mentioned my name from July…
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Haha, job queue is too big :)
antonbabenko
antonbabenkoabout 8 years ago
Yeah, they definitely have to improve the way they handle queues 🙂
U
Unknown Userabout 8 years ago
There is 1 event this week
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
CORRECTION this event has moved to 11am PST (two hours later) per popular demand
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Ping me if you want to be added to the calendar invite
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
also, if you have suggestions for managing events like this using som SaaS <---- i want to know 😃
U
Unknown Userabout 8 years ago
antonbabenko
antonbabenkoabout 8 years ago
I will try to be on this call but can’t promise today.
Andrey Devyatkin
Andrey Devyatkinabout 8 years ago
Hello to you people of SweetOps! I'm Andrey, solo consultant with focus on CI/CD, Jenkins, Docker, K8S, HashiCorp tools. Good to be here!
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
nice to meet you @Andrey Devyatkin 👏
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
@Andrey Devyatkin great to meet you! got your email too. Would love to give you a tour of everything going on as it relates to what you're working on. If that sounds interesting, drop something on my calendar here: https://calendly.com/cloudposse
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
(the same invitation goes to anyone else here! if anyone wants a tour of everything going on here at cloudposse as it relates to our Open Source initiatives, feel free to use the calendly link above to schedule a time)
Gabe
Gabeabout 8 years ago
Have you guys ever considered the name Insane Cloud Posse?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
haha we own the domain 😃
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
but not branding around it...
Gabe
Gabeabout 8 years ago
that’s awesome
antonbabenko
antonbabenkoabout 8 years ago
Hi @Andrey Devyatkin! Great to see you here 🙂
U
Unknown Userabout 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
I am running a tad late. Got locked out of my office
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
#townhall has some meeting links
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
hi all!

I wanted to say “Thank you!” for a LOT of amazing insights & ideas here (and in github repos - that’s how I got here). Though I processed only a bit, I’d already borrowed some. 🙂👍️
antonbabenko
antonbabenkoabout 8 years ago
Hi @Alexander Tolstikov! Welcome to us 🙂
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
hey @Alexander Tolstikov
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
what are you working on?
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
@Andriy Knysh (Cloud Posse) some CICD, IaC, automation, stuff like that mostly
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
what CI/CD are you using?
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
Jenkins pipelines, Gitlab CI, Travis, etc but now I’m working on some idea of making universal pipelines that are not locked into specific CICD solution and could be launched from any CICD or manually (to avoid a vendor lock and well-known complications and limits of available systems)
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
though to be honest, I don’t consider Gitlab CI & Travis as a fully blown CICD, but rather CI with some functions of CD 🙂
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
@Alexander Tolstikov we have similar ambitions for the CI/CD - reducing vendor lock-in
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
we use our https://github.com/cloudposse/build-harness to achieve this to some degree
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
I believe you already have a good foundation to do it soon, as I could see from repos
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
we use it with travis and codefresh
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
in an ideal world, every step of the build pipeline is a container. then the build-harness is a perfect compliment.
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
yep, I spent some time digging build-harness already 🙂
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
haha yea - it's pretty massive
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
TBH though we're focused mostly on Codefresh these days
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
I have to say that it changed my “world vision” a bit
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
so many CICD systems, so little time
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago(edited)
seems like Makefile is the almost perfect fit for this goal (at least I sticked to this thought these days). And with some additional wrappers and builders it could do the job perfectly.
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
do you have any particular reason to use Codefresh?
erik
erikabout 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
my favorite quote 😃
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago(edited)
I believe that I saw in this slack something like “I can iterate with it faster”, but I never had a chance to check it by myself.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
my (3) arguments for codefresh:
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
1) unlimited pipelines per repo; every step is a container. no need for complicated manifests (E.g. circle). stick all complexity in the container.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
2) tight integration with kubernetes and helm. easy 1-click deployments and rollbacks.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
3) native support for docker/docker compose. need to spin up 15 containers for CI? no problem. they'll do it.
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
4) integrated chartmuseum?
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
sounds good… But why do you need smth like Atlantis for Terraform CICD?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
hah - that's a good question
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
i'm teetering back and forth on atlantis
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
atlantis pros:
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
- purpose built CI/CD tool for terraform; I like tools that specialize
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
- chatops style interaction
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
- run atlantis inside AWS account and use instance profiles for IAM
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
atlantis cons:
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
- no easy way to do even basic acls like restricting who can run plan or apply.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
- currently no way to have multiple pipelines per repo
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
yep, I saw the proposal about multiple pipelines from you…
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
yea - haven't checked if there was any update on that
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
for now, we're going to move forward with Codefresh
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
downside with codefresh is running build agent inside of AWS account (atlantis style) requires enterprise agreement
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
since most of our customers have enterprise agreements, this is not a problem
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
anyway, I believe, that behind each “apply” on PROD environment should be a git tag, and not just some pull request approved
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
i agree with you in an ideal world
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
and didn’t see anything like that in Atlantis, but I just did a very quick check
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
for staging, however, that should not be a requirement
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
as it might not work first time around. <--- hence i like the chat ops
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
our intent is to mimick some of the atlantis behavior using this
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
whereby we comment back on PRs
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago(edited)
yep, I can see what you mean
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
also, it's unclear to me how well atlantis works in a large terraform monorepo with many projects <--- we want to only plan/apply projects that have changes
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
good point
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago(edited)
also, I believe that it is better to have separated “build” and “apply” stages for the pipeline itself too:

so, in “build” stage you apply some template processing, etc (e.g. with gomplate, etc) and create the “pipeline artifact” (e.g. commit/tag in some other repo or branch) with the final pipeline and all deps

and in “apply” stage you don’t perform any processing, but only execute command(s) on top of “pipeline artifact”

sounds like over-engineering, but I believe this is the way 🙂
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
@Erik Osterman (Cloud Posse) What is unclear ? The way it works now is that it can autoplan for projects with changes. This could mean that 3 out of 10 projects would be autoplanned for which you after can apply, and then also apply-per-project.
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
big problem is the one huge yaml
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
ok that's cool
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Also if you have modules in the same mono-repo, it would automatically autoplan all projects the moment you change the modules. I'm not sure if it actually calculates dependencies.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
@Maarten van der Hoef so in my own words, if a monorepo has aws/vpc and aws/ecs, and aws/dns folders, and I only make changes to aws/dns, it will detect that and only run plan (and eventually apply) on that
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
correct
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
nice
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
it's actually working really nice. pre-merge-apply's are confusing but it never leads to problems. The plan locking works well.
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Not having streaming output is more of an issue. I'd like to see what's happening in real time.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
what about the acl issues?
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
wdym ?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
no way to restrict who can run atlantis plan or atlantis apply
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
other than restricting access to repo altogether
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
ah that can be, hasn't been an issue for us
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
as an active user, what are your thoughts on this? https://github.com/runatlantis/atlantis/issues/249#issuecomment-422240279
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
We don't have that structure, but for the way cloudposse is doing stuff it would make it compatible. I also don't see another way how to do it otherwise,
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
thanks for the first-hand account
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago(edited)
This shouldn't involve a lot of code change in Atlantis I think, have you taken a look already @Erik Osterman (Cloud Posse)?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
I asked @alebabai to take a brief look at it
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
but haven't checked in to hear what the scope-of-work would entail.
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
in the end it's always a lot, with added testing and what not.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
hah, yea
johncblandii
johncblandiiabout 8 years ago
hey folks. didn’t know this existed. 🙂
johncblandii
johncblandiiabout 8 years ago(edited)
I’m hitting an issue with the VPC peering module. Is this the right room to discuss?
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Let’s move to #terraform
johncblandii
johncblandiiabout 8 years ago
thx
erik
erikabout 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
Such a great description of GitOps by Flux. https://github.com/weaveworks/flux
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago(edited)
so, we have GitOps for Terraform (Atlantis), and GitOps for k8s (flux), but does some universal GitOps solution exist?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Jenkins? 😊
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
j/k
loren
lorenabout 8 years ago
lulz
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
ohh, yeahh, but still needs some setup 🙂
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
So, I don't know of anything off the shelf
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
also, I believe Jenkins have some great plans for the future now 🙂
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
What I like about Codefresh, is that every step of the pipeline is a container. So if we can containerize the Business Logic, we can do it.
loren
lorenabout 8 years ago
personally i kind of think of pretty much any set of tools that executes a workflow based on PRs, merges, and tags can be considered GitOps
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Yes - i don't think flux or atlantis is technically needed. they are good purpose built tools.
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
I’d like to see some general framework for any type of “command to launch on PR approval”
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago(edited)
instead of kubectl/terraform apply launch hardcoded 🙂
loren
lorenabout 8 years ago(edited)
here's what i created to piece things together between codecommit and codebuild, https://github.com/plus3it/terraform-aws-codecommit-flow-ci
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
probably Cloud Posse will have something at some point 🙂
loren
lorenabout 8 years ago
a pull request triggers a job, a merge triggers another job, and a tag triggers a job. you define what each job-type does via your buildspec(s)
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
yep, but vendor-lock again…
loren
lorenabout 8 years ago
not really
loren
lorenabout 8 years ago
i write the jobs in a Makefile, and the buildspec just executes make targets
loren
lorenabout 8 years ago
easy enough to port to gitlab-ci or travis or whatever
loren
lorenabout 8 years ago
also, this summarizes nicely what i think of vendor lock-in, https://bravenewgeek.com/multi-cloud-is-a-trap/
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
I'm working on our requirements here: https://cloudposse.quip.com/Mb7cA97IuIm8
loren
lorenabout 8 years ago

>> The mental gymnastics I see companies go through to avoid vendor lock-in and “reasons” for multi-cloud always astound me. It’s baffling the amount of money companies are willing to spend on things that do not differentiate them in any way whatsoever and, in fact, forces them to divert resources from business-differentiating things.
loren
lorenabout 8 years ago
so many good quotes
>> When you abstract away the differentiating features to avoid lock-in, you also abstract away the value. You end up with vendor “lock-out,” which basically means you aren’t leveraging the full value of services.
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
@loren yes and no, I believe there should be “the golden mean” between totally avoiding vendor-lock and total locking, in other words, you should have some way to easy move to other provider

but, with kubernetes the issue is mitigated a lot I believe (especially with k8s-as-service)
loren
lorenabout 8 years ago
i just don't see it being that big a deal, people get way bent out of shape over the smallest thing
loren
lorenabout 8 years ago(edited)
spaces or tabs! vi or emacs! blech. just get the job done, stick with whatever the project already does.
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
looks like I (almost) always agree with you @loren 🙂
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
but better to be DRY, and don’t repeat yourself with a next job or at least be able to re-use most parts of the previous work 🙂
loren
lorenabout 8 years ago
i agree. though i always try to remember also that premature optimization is the root of all evil, and that copy-paste is often better than a bad abstraction
Alexander Tolstikov
Alexander Tolstikovabout 8 years ago
that’s true
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Max Moon
Max Moonabout 8 years ago
"new jersey style"
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
I started #chatops for those interested
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
I've started an agenda for the next Town Hall on 2018-10-03
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
antonbabenko
antonbabenkoabout 8 years ago
I will be on vacation during next Town Hall call, so talk without me.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Ok!
U
Unknown Userabout 8 years ago
There are no events this week
Mark Johnson
Mark Johnsonabout 8 years ago
Anyone know if TF supports disabling/enabling STS regions? I've been googling and can't find anything ...
Mark Johnson
Mark Johnsonabout 8 years ago
Also -- Anyone have link to some cool global AWS organization TF stuff for small/mid/medium sized ORGS in terms of things being applied everywhere (e.g. cloudtrail, config, some global roles, etc.)
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Hey @Mark Johnson
Mark Johnson
Mark Johnsonabout 8 years ago
Yo
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
not sure if it’s cool 🙂 but here is what we usually do https://docs.cloudposse.com/reference-architectures/
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Mark Johnson
Mark Johnsonabout 8 years ago
awesome
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
terraform-root-modules is our collection of TF modules that we usually deploy
Mark Johnson
Mark Johnsonabout 8 years ago
Looking at that one now
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
root, testing, staging, prod etc. are our reference architectures for the stages, they don’t have any code, they are just identities, we deploy them do different AWS accounts
Mark Johnson
Mark Johnsonabout 8 years ago
gotcha checking it now
Rohit Verma
Rohit Vermaabout 8 years ago
hi all, any recommendation on vpn setting, which allow resolving private route53 dns records locally. I have tried this https://github.com/kylemanna/docker-openvpn, along with bind instructions from here https://www.youtube.com/watch?v=xeIWpyst0P4. On my local use tunnelblick to connect. Couldn’t mac the setup working though, got connected to vpn and can use private ips, but dns resolution still not workable. Tried adding nameserver also manually, no luck.
Rohit Verma
Rohit Vermaabout 8 years ago
@Erik Osterman (Cloud Posse) @Andriy Knysh (Cloud Posse) Any leads on above
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
have you seen our bad ass chart for this?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
this supports GitHub SSO + shortlived open vpn keys
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
It could use some dusting off - but here to help if you want to
Rohit Verma
Rohit Vermaabout 8 years ago
this is required for an old environment, there is no kubernetes there
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
😢
Rohit Verma
Rohit Vermaabout 8 years ago
this image cloudposse/openvpn, can you share code?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Rohit Verma
Rohit Vermaabout 8 years ago
I don’t see any usage of bind, are you sure client can resolve route53 entries, e.g. from my local if I try private.internal.api ( internal.api=private hosted zone), will it work?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
so the traffic is NAT’d from internal ec2 instance
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
so it has the internal-view for route53
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
it also resolves kube-dns
Rohit Verma
Rohit Vermaabout 8 years ago(edited)
you mean from my local I can call svc directly, e.g curl <http://alertmanager-operated.monitoring.svc.cluster.local>
Rohit Verma
Rohit Vermaabout 8 years ago
but how your local nameservers are updated? which openvpn client you used?
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
that’s a DHCP setting
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
-n $(cat /etc/resolv.conf | grep -i nameserver|head -n1|cut -d ' ' -f2)
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
as argument to ovpn_genconfig
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
@Rohit Verma ☝️
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Suggest breaking it apart into what and why
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Reading the description it’s not clear what it does does, but more why it does it
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
What ~ like how it works
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
good idea, thanks
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Ping me when you update it and I’ll Re review :)
G
GreetBotabout 8 years ago
@channel hey everyone give a warm welcome to @jonboulle! Good to have you here ☺️
antonbabenko
antonbabenkoabout 8 years ago
Hi @jonboulle!
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
hi @jonboulle 🙂
jonboulle
jonboulleabout 8 years ago
whoa lots of welcomes
jonboulle
jonboulleabout 8 years ago
o/
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
@jonboulle What brings you around?
jonboulle
jonboulleabout 8 years ago
maarten 😉
Maarten van der Hoef
Maarten van der Hoefabout 8 years ago
Jon replaced me at Blinkist and also works on the ecs airship modules, although he actually is more of an K8S guy.. @jonboulle maybe you can share some more info's.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Haha ok, well you are amongst friends :) we do lots of k8s and terraform
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
Hopefully you can join our next town hall zoom call which is next Wednesday 11am PST
Z
Zapierabout 8 years ago
@Mark Mutti created a new channel #aws. Join if this sounds interesting!
G
GreetBotabout 8 years ago
hey everyone give a warm welcome to @Andy! Good to have you here ☺️
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago(edited)
Hey @Andy! let me know if there's anything we can help out with.
G
GreetBotabout 8 years ago
hey everyone give a warm welcome to @Daz! Good to have you here ☺️
dennybaa
dennybaaabout 8 years ago
Hi everybody! It's pleasure to hang out here.
@Rohit Verma Hey, there's an easy "openvpn" way with pritunl, https://pritunl.com/ , users can be configured via web if it suits you. Also making a k8s deployment/chart for pritunl should be very easy, it uses mongo which is the only which will require a pvc...
dennybaa
dennybaaabout 8 years ago
all the dns, dhcp you get out-of-the-box
Rohit Verma
Rohit Vermaabout 8 years ago
@dennybaa Thanks for suggesttion, this is really nice. I tried and it was working as expected.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)about 8 years ago
@dennybaa that is a great suggestion. I forgot about it.
G
GreetBotabout 8 years ago
hey everyone give a warm welcome to @vitaly.markov! Good to have you here ☺️
G
GreetBotabout 8 years ago
hey everyone give a warm welcome to @praveen! Good to have you here ☺️
Andriy Knysh (Cloud Posse)
Andriy Knysh (Cloud Posse)about 8 years ago
hey @vitaly.markov and @praveen, what are you working on?