Saarko

Results 24 issues of Saarko

This template is still work in progress, however, as a reminder for ourselves to fine tune the prometheus export. [Template link](https://github.com/sando38/eturnal/blob/grafana/config/grafana-prometheus.json) Current look and feel: ![2023-06-20_09-00](https://github.com/processone/eturnal/assets/90323876/6dda8526-503c-40f8-8f76-f4ea82066a15) ![2023-06-20_09-01](https://github.com/processone/eturnal/assets/90323876/61ec3ab5-6572-4bf2-963e-d8e8cd46e394)

enhancement

This action needs a personal access token with 'delete:package' capacity defined as a secret for this repository. Secret name is PAT_TOKEN . This will delete all test/ edge container images...

enhancement
containers

Currently bucket sizes for time and data are hard coded. These values are tailored for Audio/Video use cases, however, TURN is not only used for these scenarios. Therefore, provide a...

enhancement

If we deploy eturnal in managed kubernetes environments, we require a loadbalancer service, which forwards the traffic to eturnal. These traffic will not have the real IP address of the...

enhancement

In certain scenarios, a TURN server communicates with itself. This is done through the UDP stack. To be more effective eturnal should detect such cases and avoid using the UPD...

enhancement

Currently the I/O data is updated by the end of TURN session. This works generally well. However, a live view would improve for example views on peaks in I/O, whereas...

enhancement

It would be nice to also configure the agent to use a socket proxy like the main app can: Swarmpits behavior can be reconfigured via Environment Variables. SWARMPIT_DOCKER_SOCK Docker SOCK...

### Proposal Currently the operator creates a database headless-service with roughly these configs: ```yaml apiVersion: v1 kind: Service metadata: name: database-pxc-db-pxc spec: ports: - name: mysql protocol: TCP port: 3306...

jira_task

The output generated by https://github.com/processone/rtb#xmpp-scenario is not compatible with the current database schema.

**Describe the feature request** Currently, if I have cluster external ingress via a `gateway`, the traffic from the `gateway` to a `waypoint` enabled service does not go through the `waypoint`...

kind/enhancement
area/networking
area/ambient