Dmitry Nutels

Additional information... Installing `alb-a` and `alb-b` controllers into different namespaces doesn't work either. After installing `alb-a` into `infra-a` namespace (worked fine), while trying to install `alb-b` into `infra-b` namespace: ```...

Thank you for clarifying, I somehow missed that one. It's somewhat academic. The main use case it to be able to configure the controller differently for different namespaces/ingress classes. I...

Actually, it wouldn't work even with this minimal setup: ```yaml receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:4317 processors: batch/metrics: timeout: 1s send_batch_size: 50 exporters: logging/metrics: loglevel: debug service: pipelines: metrics: receivers:...

Correct me here, but without this flag, these are currently not collected or shipped from the receiver forward. My thinking was -- since, at this point, the receiver is a...

Hi guys. Are there, by chance, any updates on how this is progressing and an estimate, hopefully?

Here we are, 2017, and the problem hasn't gone away. Consider the following - components, each with their own `render` method, being `require`d by the main app. ``` const dust...

@NickHeiner How would that work? The `resolve` would trigger the task?

@NickHeiner That's what I thought you had in mind. You'd need a finer granulation though - per task, probably, rather than per entire config. And without having to envelope all...

I think the time has come for me to inquire on the progress in this direction. Is there any :)?

Indeed. `html-webpack-plugin` is at `@next` (which is 4.0.0) and it doesn't work with this or `inline-manifest-webpack-plugin`