Julian Tölle

Results 34 issues of Julian Tölle

## Scenario - Cluster CIDR in hccm config does not correspond to real Pod CIDRs - Routes are created for real Pod CIDRs - Nodes are removed again by an...

bug
pinned

We are sending a request every ten seconds to Hetzner Cloud API if the routing functionality is active (default when Networking is activated). This equals 1/10th of the default API...

bug
pinned

## 52-bit IDs Our API documentation specified the type for all ID fields as `integer`. We have realized that this was not sufficient and that some users of our API...

pinned

### TL;DR It's not possible to configure the services health check options in `hcloud load-balancer add-service`. This is only possible through [`update-service`](https://github.com/hetznercloud/cli/blob/5083734ac9b2cebaa8c71c8fda8fa46e1b35ba96/internal/cmd/loadbalancer/update_service.go#L40-L51) right now. ### Expected behavior I would expect...

feature

### TL;DR The current docs do not describe how to use certificates with load balancers. Users need to read the annotations (reference) to figure this out. ### Expected behavior We...

enhancement
documentation

### What whould you like to see? There are some cases where we need to shutdown the server to apply updates to it: - Changing Server Type - Adding to...

enhancement

We can remove the [workaround to always set `AWS_XRAY_DAEMON_ADDRESS`](https://github.com/narando/nest-xray/blob/3c8c7db459b6e688228156d6d2cbbf5d24a77d44/lib/core/tracing.service.ts#L16-L22) as the aws-sdk-node fixed a bug where the used http clients would not be updated after calling `.setDaemonAddress` (upstream bug: https://github.com/aws/aws-xray-sdk-node/issues/233)....

The new `aws-xray-sdk@3` switched from `continuation-local-storage` to `cls-hooked` and now supports the automatic mode in `async/await` functions. We should be able to replace our local ["fake automatic mode"](https://github.com/narando/nest-xray/blob/3c8c7db459b6e688228156d6d2cbbf5d24a77d44/lib/core/tracing.service.ts#L41-L43) with the...

enhancement
help wanted

The Nest.js Microservice pattern is currently not supported out-of-the-box and requires manual setup to trace incoming and outgoing calls. ## Todo 1. Create `Interceptor` to setup `AsyncContext` + Tracing Segment...

enhancement
help wanted

This separates accessing the cache from loading the data and renames some identifiers to better represent their purpose.