Malte Granderath

When a container fails while being built the error is never shown to the user.

Currently, the deploy hook depends on the domain to send the HTTP Request. We should be able to find a better way to do this.

When first starting spaas without a config preconfigured this error is printed. ``` While parsing config: unexpected end of JSON input ``` This doesn't have any implications on the functionality

Allow the user to connect their instance to a database.

fixing TLS configuration for http clients

2

As reported in [this issue](https://github.com/apache/pinot/issues/13431) there is an issue where the created HttpClients do not respect the TLS configuration. This fixes that bug.

Apache HttpClient does not respect TLS configuration

2

During our attempted upgrade to 1.1.0 we noticed that some calls from the controller to the servers were failing due to TLS issues. We have 2-way TLS configured for our...