Trey Hyde

I might be seeing something similar. It creates a route with netmask of /17 which will only get 50% of the /16 the is the kube VPC.

> The labels are: > > ``` > failure-domain.beta.kubernetes.io/zone=us-east-1a > failure-domain.beta.kubernetes.io/region=us-east-1 > ``` > > Which follows what written in Kubernetes [docs](https://kubernetes.io/docs/reference/kubernetes-api/labels-annotations-taints/#failure-domainbetakubernetesiozone) > > I'll try to change the classification...

Just a note for the discussion. Same zone traffic incurs a cross-zone charge if it traverses a VPC boundary. (actually, 2 charges, in and out) Based on the docs, I...

> Right now, the implementation does not use any provider specific data for classification. It has been a discussion point, but the nuances across providers are not always 1-1. This...

> @treyhyde you can see a mapping between source pod name and destination IP / zone in the frontend UI (Allocation --> network drilldown). Is this view generally useful or...

> @treyhyde What you're seeing the network-costs logs are similar to what you're seeing in the frontend UI. The view of the data is limited to the lifetime of the...

Happy to provide anything. The kubecost UI is devoid of anything really useful but the kubecost-network-costs-* logs are a treasure trove but difficult to reassemble. I haven't yet looked at...

I make extensive use of triggering pipelines via cloudevents delivered from knative... so that works... but I'm forced to disable retry since knative thinks all the responses are bogus regardless...

We'd love to use kogito as a service component in a multi-tenant SaaS application. These sorts of issues mean we are swimming up stream. It doesn't just seem to be...

Sure, we want to allow customers to manager real life business processes and cases in a less bespoke way. BPMN and CMMN are good fits at a high level We'll...