route "stdout" contains reference to undefined or misconfigured template "raw-json"." #496
Comments
|
@AndreyLevchenko can you take a look at this? |
|
Hello @gsoeldner You can check your config file, does this file have Can you also tell which version of Regards, Dmitriy |
|
Hi Dmitry, we are using 2.9.0...we used the values.yaml as and removed all the unnecessary stuff: Best |
|
Here is the config: Installation: helm install app -n postee aqua/postee --values values.yaml#################################################### values.yaml posteUi: Default values for postee.This is a YAML-formatted file.Declare variables to be passed into your templates.replicaCount: 1 The configuration file contains a general settings section,routes, templates and actions sections.name: aqua-test # The tenant name Routes are used to define how to handle an incoming messageroutes:
Templates are used to format a messagetemplates:
Actions are target services that should consume the messagesactions:
|
|
Hello @gsoeldner Can you check config log(start of Postee)? my configuration example: |
|
Hi, here is the thconfig log: 2022/11/21 14:18:12 Starting Router.... |
|
Hello! Thanks a lot. Looks like there is problem with access to templates. can you try to get list of templates in example commands(on my PC): ➜ kubectl get pods -n postee2
NAME READY STATUS RESTARTS AGE
app-postee-0 1/1 Running 0 6m30s
app-posteeui-68955bc58c-9775c 1/1 Running 0 6m30s
➜ kubectl exec -it --namespace postee2 app-postee-0 /bin/sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Defaulted container "postee" out of: postee, setting-db (init), setting-cfg (init)
/server $ ls -hl /server/rego-templates/
total 60K
drwxr-xr-x 1 postee postee 4.0K Sep 14 23:26 common
drwxrwxrwx 2 root root 4.0K Nov 22 05:33 custom
drwxr-xr-x 1 postee postee 4.0K Sep 14 23:26 example
-rw-r--r-- 1 postee postee 199 Sep 14 23:26 raw-message-html.rego
-rw-r--r-- 1 postee postee 93 Sep 14 23:26 raw-message-json.rego |
|
Hi, here is the output: |
|
I was able to get a similar error: 2022/11/24 03:57:11 Configuring template raw-html
2022/11/24 03:57:11 Can not initialize template raw-html: 1 error occurred during loading: open rego-templates/custom/123: permission denied can you check Remove |
|
Hi, |
|
Hello @g-soeldner Can you do one more experiment: persistentVolume:
enabled: false
mountPathDb: /server/database
mountPathConfig: /data
mountPathRego: /server/test/custom
mountPathFilters: /server/rego-filters/custom
accessModes:
- ReadWriteOnce
size: 1Gi
annotations: {}And install postee with this change. |
|
Ok that helps...but next Problem: Error while sending event: Post "https://hecendpoint:8088/services/collector": x509: certificate signed by unknown authority How can we ignore the warning? |
|
Looks like you need to install and update Postee currently has |
|
Well that is pretty complicated without being root. |
|
I found that helm provide Can you try install postee with this flag? |
|
You mean this here: We can use the chart, however we do not know how to import our ca-certificate into the app-postee-0 pod. |
|
if i understand correctly - you can add certificate using |
|
No, the installation is not the problem. We need to bring our certificates into the Pod in order to talk to Splunk....see here: Two solutions:
|
|
hm... you are right. It makes sense. |
|
We need it for Splunk not for the slack action |
|
There seems to be a merge into Postee for Enterprise branch...tls-verify-skip for Splunk. We really need it super super super urgent the new release!!!!! |
|
oh... my mistake... I created #505. We will try to merge it as soon as possible. |
|
Hello All, What I want__: Not to collect logs into container log by Postee but send out only the scan reports to webhook/recipents. |
|
Hello @linthoisana I thinks it is different issue. |
|
thank you @DmitriyLewen . i have created an issue #507 |
|
@DmitriyLewen do you have any updates to share regarding this issue? |
|
Hi we are using Postee and run into the same issue where |
|
Hello, +1. |
|
We could change the code so that certain folders can be ignored when recursively scanning for REGO templates. |
|
Hello @smangels , @stanislavdip I created filter for rego-templates by Can you check this changes? Also I have 1 more request - can you send me permissions for Regards, Dmitriy |
|
Hello @DmitriyLewen Here are the permissions for the files: |
|
Hello @g-soeldner , @smangels , @stanislavdip We merged #556. Regards, Dmtriyi |
Description
What did you expect to happen?
The installation succeeded. We expected to see results of the scan in the container log.
What happened instead?
We received error from the logs regarding the template.
Output of run with
POSTEE_DEBUG=true:#################################################
ERROR MESSAGE
#################################################
{
insertId: "q35i4olmi0ay1o75"
labels: {5}
logName: "projects/t-2004107-aquaops-0000/logs/stderr"
receiveTimestamp: "2022-11-16T10:55:12.840010372Z"
resource: {2}
severity: "ERROR"
textPayload: "2022/11/16 10:55:08 route "stdout" contains reference to undefined or misconfigured template "raw-json"."
timestamp: "2022-11-16T10:55:08.364027297Z"
}
Additional details (environment setup, networking info...):
We copied the yaml file from the GitHub page and checked it several times. There are no syntax errors inside. Also the config map after the deployment exactly resembles the documentation.
The text was updated successfully, but these errors were encountered: