5 ms·

So are you saying that, no matter what, if you want to reply your whole infrastructure as code (networks, dmz, hosts, services, apps, backups etc ) that you are

So are you saying that, no matter what, if you want to reply your whole infrastructure as code (networks, dmz, hosts, services, apps, backups etc ) that you are going to have to reproduce that somehow (whatever the combo of AWS services are, OR just learn K8S Effectively, "every infrastructure as code project will reimplement Kubernetes in Bash"

silviogutierrez 6y ago
Exactly. That's a great way to put it. A bunch of Bash glue reimplementing what Kubernetes already does. Poorly.
- roman_sf 6y ago
  Kubernetes is outstanding because proving ol bash scripts were bad and re-writing all Bash glue in Go glue, slapping 150 APIs on top (60 "new" and about hundred "old versions" https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18 https://kubernetes.io/docs/reference/generated/kubernetes-ap...), adding few dozen opensource must have projects - so finally it can be called "cloud native" - boom, a new cloud native bash for the cloud is born!
  - tannhaeuser 6y ago
    Actually it's worse than that - k8s was ported from Java, and the codebase is an incoherent mess, as k8s devs say themselves
- gfodor 6y ago
  Bash glue has rarely failed me. Never used k8s, but the horror stories I hear ensure I won’t feel dirty for writing a little bash to solve problems anytime soon.
aprdm 6y ago
Not necessarily. You can have all of above with Terraform, Ansible, Puppet, Chef... etc.
- verdverm 6y ago
  Instead of a varied interface tools set, I can have one with consistent interfaces and experiences. Kubernetes is where everything is going, hence why TF and Ansible have both recently released Kubernetes related products / features. It's their last attempt at remaining relevant (which is more than likely wasted effort in the long run). They have too much baggage (existing users in another paradigm) to make a successful pivot.
  - Multicomp 6y ago
    Ironically for me, those two tools are part of the blessed triad that we use for all of our infrastructure as code and end-user virtual machine initial setup. If we only got to keep two tools it would be kubernetes and terraform.
  - aprdm 6y ago
    Last attempt at remaining relevant - lol. This isn’t a competition, they are tools. Ansible is widely used and will continue to be so for a long long time. Its foundations - ssh, python and yaml are also in for the long run to manage infrastructure...
    - verdverm 6y ago
      Yaml is on the way out, Cuelang will replace it where it's used for infra. It's quite easy to start by validating yaml and then you quickly realize how awesome having your config in a well thought-out language is!
      - aprdm 6y ago
        I thought you were trolling with some called Cuelang but is actually a thing. Yaml will still be used in 100 years, k8s is yaml based...
        verdverm 6y ago
        Yes but YOU won't be writing or seeing yaml, Cue will output the yaml and run kubectl (I'm already doing this to great relief) Which is step 2 of my Enterprise adoption strategy. Step 1 is starting with validation, step 3 and beyond is where the real fun starts!
deleted 6y ago
[deleted]

silviogutierrez 6y ago

Exactly. That's a great way to put it. A bunch of Bash glue reimplementing what Kubernetes already does. Poorly.

roman_sf 6y ago
Kubernetes is outstanding because proving ol bash scripts were bad and re-writing all Bash glue in Go glue, slapping 150 APIs on top (60 "new" and about hundred "old versions" https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18 https://kubernetes.io/docs/reference/generated/kubernetes-ap...), adding few dozen opensource must have projects - so finally it can be called "cloud native" - boom, a new cloud native bash for the cloud is born!
- tannhaeuser 6y ago
  Actually it's worse than that - k8s was ported from Java, and the codebase is an incoherent mess, as k8s devs say themselves
gfodor 6y ago
Bash glue has rarely failed me. Never used k8s, but the horror stories I hear ensure I won’t feel dirty for writing a little bash to solve problems anytime soon.

aprdm 6y ago

Not necessarily. You can have all of above with Terraform, Ansible, Puppet, Chef... etc.

verdverm 6y ago
Instead of a varied interface tools set, I can have one with consistent interfaces and experiences. Kubernetes is where everything is going, hence why TF and Ansible have both recently released Kubernetes related products / features. It's their last attempt at remaining relevant (which is more than likely wasted effort in the long run). They have too much baggage (existing users in another paradigm) to make a successful pivot.
- Multicomp 6y ago
  Ironically for me, those two tools are part of the blessed triad that we use for all of our infrastructure as code and end-user virtual machine initial setup. If we only got to keep two tools it would be kubernetes and terraform.
- aprdm 6y ago
  Last attempt at remaining relevant - lol. This isn’t a competition, they are tools. Ansible is widely used and will continue to be so for a long long time. Its foundations - ssh, python and yaml are also in for the long run to manage infrastructure...
  - verdverm 6y ago
    Yaml is on the way out, Cuelang will replace it where it's used for infra. It's quite easy to start by validating yaml and then you quickly realize how awesome having your config in a well thought-out language is!
    - aprdm 6y ago
      I thought you were trolling with some called Cuelang but is actually a thing. Yaml will still be used in 100 years, k8s is yaml based...
      - verdverm 6y ago
        Yes but YOU won't be writing or seeing yaml, Cue will output the yaml and run kubectl (I'm already doing this to great relief) Which is step 2 of my Enterprise adoption strategy. Step 1 is starting with validation, step 3 and beyond is where the real fun starts!

deleted 6y ago

[deleted]