mhemken-vts

Hold on... there's no such thing as `apply`? Am I having a case of the Mandela Effect? I swear I've used `eksctl apply` before. How was this not a thing...

> We might eventually support `apply`, but there are many features that have precedence. Like, as supporting Karpenter out of the box, for example, allowing users to explore and use...

Hostmetrics is required for us to use otelcol to send metrics to datadog. Would be nice if we could use ADOT out of the box for this use case.

Can ALL the resource settings be exposed please? * [destination-stdin][dststdin] * [source-stdout][srcstdout] [dststdin]: https://github.com/airbytehq/airbyte-platform/blob/f2819ce4a990c783581cdc770c39ebed6161d800/airbyte-server/src/main/resources/application.yml#L189 "stdin" [srcstdout]: https://github.com/airbytehq/airbyte-platform/blob/f2819ce4a990c783581cdc770c39ebed6161d800/airbyte-server/src/main/resources/application.yml#L204 "stdout"

When using Hashicorp's Kubernetes provider using the exec configuration the API version remains `v1alpha1` even when we explicitly set it to `v1beta1`. The flag I'm looking for is `--force-v1beta1-I-dont-give-a-damn`.

I think I'm running into an issue with this as well. I create a file in one container and add to a different container so I can `flux push artifact`....

Yeah this would really help me figure out how to call a particular remote state without having to go into full detective mode.

Any update?