You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Failed to save resource: admission webhook "validations.kong.konghq.com" denied the request: plugin failed schema validation: schema violation (config.resource_attributes: expected a string)
Following the Opentelemetry Documentation I have tried to set the service.name key pair, but run into the webhook validation issue.
This is tied to the Kong/kong#10654, which stated was fixed in Kong 3.4, but we are still running into this issue.
Expected Behavior
I expect the manifest to be created while using the service.name key pair.
Steps To Reproduce
Steps To Reproduce
(Optionally) Enable the OpenTelemetery plugin within Kong's configuration.
Within Kubernetes, enable Kong's validating admission Webhook via a ValidatingWebhookConfiguration.
Attempt to create a KongPlugin object by applying a manifest like the one shown earlier, via kubectl apply --filename --dry-run=server or kubectl apply --filename --server-side=true.
Observe that the validating Webhook rejects the manifest due to the "config.resource_attributes" mapping entry.
Kong Ingress Controller version
2.12
Kubernetes version
Anything else?
Anything else?
This might be resolved for the Log-File plugin for custom_fields_by_lua,
But it is not fixed for OpenTelemetry.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
Is there an existing issue for this?
Kong 3.4.0
Failed to save resource: admission webhook "validations.kong.konghq.com" denied the request: plugin failed schema validation: schema violation (config.resource_attributes: expected a string)
Following the Opentelemetry Documentation I have tried to set the service.name key pair, but run into the webhook validation issue.
This is tied to the Kong/kong#10654, which stated was fixed in Kong 3.4, but we are still running into this issue.
Expected Behavior
I expect the manifest to be created while using the service.name key pair.
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
Anything else?
This might be resolved for the Log-File plugin for custom_fields_by_lua,
But it is not fixed for OpenTelemetry.
The text was updated successfully, but these errors were encountered: