NoodlesWang2024 opened a new pull request, #163:
URL: https://github.com/apache/skywalking-helm/pull/163
**Bug Description**
We've encountered an issue where the OAP server fails to start in init mode
when custom Kubernetes metrics are enabled. The same configuration works
perfectly for the server in no-init mode (the standard deployment).
The root cause appears to be an inconsistency in how the custom metrics
files are mounted between the init Job and the standard Deployment.
**Steps to Reproduce**:
Define custom Kubernetes metrics in .yaml files.
Place the metric files into the K8s/ directory to be mounted into the pods.
Deploy the chart.
**Expected Behavior**:
Both the init mode OAP server (Job) and the no-init mode OAP server
(Deployment) start successfully.
**Actual Behavior**:
The standard OAP server pods (from oap-deployment.yaml) run successfully.
However, the init-mode pod (from the Job template) fails with the following
error, as it cannot find the mounted metric files:
```
org.apache.skywalking.oap.server.core.UnexpectedException: Some
configuration files of enabled rules are not found, enabled rules:
[k8s/*{.yaml,.yml}]
```
**Analysis**:
Upon inspecting the Helm templates, I found that the volume mount
configurations in the OAP Job template differ from those in the
oap-deployment.yaml.
I believe these configurations should be made consistent to ensure that both
the Job and the Deployment pods could run successful.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
