-
Notifications
You must be signed in to change notification settings - Fork 672
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
How to customize envoy access log #6676
Labels
kind/question
Categorizes an issue as a user question.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
Comments
shenshanyoumu
added
kind/question
Categorizes an issue as a user question.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
labels
Sep 18, 2024
When using a gateway provisioner, Contour can be configured through kind: GatewayClass
apiVersion: gateway.networking.k8s.io/v1beta1
metadata:
name: mygatewayclass
spec:
controllerName: projectcontour.io/gateway-controller
parametersRef:
kind: ContourDeployment
group: projectcontour.io
name: contour-with-envoy-deployment-params
namespace: projectcontour
---
kind: ContourDeployment
apiVersion: projectcontour.io/v1alpha1
metadata:
namespace: projectcontour
name: contour-with-envoy-deployment-params
spec:
runtimeSettings:
envoy:
logging:
accessLogFormat: json For more information, refer to: |
Tnanks for your help, I will check docs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/question
Categorizes an issue as a user question.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
What question do you have?:
I follow docs: [https://projectcontour.io/getting-started/] with Option 3: Contour Gateway Provisioner to install contour in projectcontour namespace it works well;
but when I follow below docs to customized envoy access logs, where is config file I can found?
https://projectcontour.io/docs/main/config/access-logging/#customizing-access-log-format
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: