The Wayback Machine - https://web.archive.org/web/20210710154155/https://github.com/topics/infrastructure-as-code
Skip to content
#

infrastructure-as-code

Here are 1,142 public repositories matching this topic...

jouve
jouve commented Jun 3, 2021

Description

let's say I have an apache process group I want to control.

  • when using supervisord.running, the name must be apache:* (which is the same notation used by supervisor)
  • when using supervisord.dead, the name must be apache: (without the *)

As both states mirror each other, I expect them to use the same convention for name, the one from running since it

anguslees
anguslees commented Mar 21, 2018

Garbage collection works by listing everything with the gc-tag. In a busy cluster, we really want that filter to happen server-side and ideally using an index of some sort.

That means we should use a Kubernetes label, not an annotation.

I think this will require a two-step migration plan (write both but continue to read annotation; release; drop support for annotation; release).

Improve this page

Add a description, image, and links to the infrastructure-as-code topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the infrastructure-as-code topic, visit your repo's landing page and select "manage topics."

Learn more