Jochen Ehret

Any progress on this issue? We are just trying to `knctl deploy` a service which has a non-standard health endpoint. It would be very helpful if we could configure the...

Hi @cppforlife, I think we need host, scheme, path and port for now.

I've tried to use `count = 0`, but then you have to use an index wherever `cf_router_lb` is used. (`cf_router_lb[0]`). That would complicate the _override file approach. A better solution...

No update currently from my side. I can't promise that I can fully implement this feature (with the `--lb-type` option)...

We've set up a Cloud Foundry landscape with bits-service on AliCloud to check which load the bits-service can handle. Test setup: cf-deployment v12.39.0 All CF VM sizes are vm_2cpu_4gb (except...

We've repeated the load tests with fog-aliyun 0.3.15. **Test setup**: CF v12.39.0 with 4 api and 2 cc-worker nodes of type "vm_2cpu_4gb". Load test runs #NUMBER_APPS parallel "cf push" processes....

We've repeated the performance tests with fog-aliyun 0.3.17 and the same setup as described in the previous comment: | NUMBER_APPS | RESOURCE_FILE_SIZE_MB | CC overall req/sec | CC avg CPU...

We've validated this PR on an AliCloud landscape and found no problems. PR was merged into capi-release 1.188.0 for testing. Change of `provider::service` syntax (PR https://github.com/fog/fog-aliyun/pull/155) is not required.

The new ops file has actually no direct relation to a FIPS stemcell: ``` - type: replace path: /stemcells/- value: alias: default os: ubuntu-jammy version: "1.406" ``` That's because the...

I'll check this proposal together with the capi developers. **Update:** We'll discuss in today's TOC meeting how to proceed.