I need to define env-vars in the sidecar runtime-env in order to make SQS calls go via a http-proxy.
This is not possible today.
it could have syntax of dapr.io/env/varname=value and be placed in the annotations.

/area runtime

Describe the feature

Allows for controlling env-vars of the sidecar.

Release Note

Implement + update docs.

If you want to work with a complete socket address type including port, we have a helper in SocketAddress. However, the moment you want to talk only about an IP address we force you to hold an in_addr or in_addr6 structure: hardly the friendliest versions of these data types.

We should provide a helpful wrapper IPAddress type that can be converted into those types as needed. This would

If you are using gnet in your projects and willing to display the name of your project or corporation on the home page, please feel free to open a PR for it.

This is where I show the user cases: User cases of gnet for English, gnet 用户案例 for Chine

in version 2.0 metadata portion of ScaledJob template is ignored so it is impossible to setup a label for job to be created

Use-Case

To support managed identity in AKS, a label "aadpodidbinding" has to be added to the object that needs pods to be running under managed identity.

To use ScaledJob to create pods that run under managed identity, ScaledJob should support metadata se

Basically, we don't need to have kafka-console-consumer, we have mill instead: https://github.com/ThreeDotsLabs/watermill/tree/master/tools/mill

It would be nice to replace it in all examples.

我看到可以通过Prometheus搭建监控环境，如果有图文，更容易理解．

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi

Increase code coverage for knative.dev/eventing/pkg/apis/flows/v1/parallel_validation.go

Expected Behavior

Stated goal for the V0.2 release is >70% test coverage.

Actual Behavior

Some packages do not meet this goal. See https://testgrid.knative.dev/eventing#coverage&sort-by-failures=

Expands on knative/eventing#591

/good-first-issue