-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement File Provider #1001
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
+1 |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Jotting down some thoughts here
Kubernetes as a provider.The provider noun could be broken down into two parts
So by default we support
We can add support for
|
cc @cpakulski |
Relates to envoyproxy#1001 & envoyproxy#1035 Signed-off-by: Arko Dasgupta <[email protected]>
* design: Run Envoy Gateway locally on host Relates to #1001 & #1035 Signed-off-by: Arko Dasgupta <[email protected]> * lint Signed-off-by: Arko Dasgupta <[email protected]> * lint Signed-off-by: Arko Dasgupta <[email protected]> --------- Signed-off-by: Arko Dasgupta <[email protected]>
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Track on #1393 |
Currently, the EnvoyProxy API defines a File provider. This provider should be implemented or removed.
The text was updated successfully, but these errors were encountered: