Mark Fisher

> I think the best way to do this (without the Pod contacting the API) would be to provide a Kubernetes controller that uses a shared Informer to capture all...

can you list your `spring.cloud.kubernetes.*` properties?

`spring.cloud.kubernetes.reload.enabled` is false by default

even though it's technically separate from this issue, once https://github.com/spring-cloud/spring-cloud-commons/issues/605 and/or https://github.com/spring-cloud/spring-cloud-config/issues/1439 is available, that would allow application config to be updated in an eventually consistent manner while relying on...

We have discussed supporting an option for eagerly fetching resources (at the time of registration) which would then or course mean failing fast in case of invalid resources.

Now that `spring-cloud-bus` builds on `spring-cloud-stream`, this would require a `Binder` implementation for SQS/SNS. Of course that would mean it would be generally useful for a wide range of `spring-cloud-stream`...

Definitely the SI adapters should be used by the `Binder`. This doc seems to provide quite a bit of info for the SNS-->SQS connection.

maybe a qualifier instead of just the bean name?

should this be an added `update()` method?... perhaps with an `AppUpdateRequest` instead of the `AppDeploymentRequest` that is expected by `deploy()`

Our goal with the deployer project is for it to be a common library for anyone needing to deploy applications (especially boot applications) across multiple platforms via a common abstraction....