-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
## Description
Some project solutions are broken / missing from certified user data, and we have an error message next to those projects.
Screenshot
Projects with broken solution a…
-
Description:
Recently, we noticed that during the Envoy initialization, there is a race condition between when TLS is configured on a upstream cluster (like validation context) and when active health…
-
Hello there!
Some time ago I and @dok441 discussed some features/changes that can be implemented to improve the karma system. So here they are (if something is already implemented then sorry ;) ):
…
-
Is relevant for services outside of Kubernetes, which do not have other health checking mechanisms.
Active health checking in Envoy:
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview…
-
## Transforming Patient Management with Salesforce Health Cloud
In today's rapidly evolving healthcare landscape, digital agility is no longer optional—it's essential. Healthcare providers and …
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help t…
-
## Enhancement Task
We have many deprecated codes which have been kept for a long time. We can clean them up.
-
I am not positive on the best solution for this, but I'd like to see some sort of option that can be enabled to block API access to a node if the head is too far behind the current head/time.
This …
-
Hi. I'm using docker-compose.yml from master, and getting error:
namenode | - Setting yarn.resourcemanager.scheduler.address=resourcemanager:8030
namenode | - Setting yarn.resourcemanager.address=re…