splunk / splunk-operator

Splunk Operator for Kubernetes
Other
210 stars 115 forks source link

Splunk Operator: OpenJDK Functionality baked into Operator #1215

Open skirven4 opened 1 year ago

skirven4 commented 1 year ago

Please select the type of request

Feature Request

Tell us more

Describe the request

Expected behavior

Splunk setup on K8S

Reproduction/Testing steps

K8s environment

K8s collector data(optional)

Additional context(optional)

gjanders commented 6 months ago

I tested this on operator 2.5.2 and found: │ TASK [splunk_common : include_tasks] *** │ │ included: /opt/ansible/roles/splunk_common/tasks/install_java.yml for localhost │ │ Tuesday 30 April 2024 05:18:59 +0000 (0:00:00.062) 0:00:06.076 * │ │ Tuesday 30 April 2024 05:18:59 +0000 (0:00:00.023) 0:00:06.099 │ │ Tuesday 30 April 2024 05:18:59 +0000 (0:00:00.023) 0:00:06.123 │ │ │ │ TASK [splunk_common : Install Openjdk11 JDK] *** │ │ included: /opt/ansible/roles/splunk_common/tasks/java_tasks/install_openjdk11_jdk.yml for localhost │ │ Tuesday 30 April 2024 05:18:59 +0000 (0:00:00.047) 0:00:06.170 * │ │ │ │ TASK [splunk_common : Create a dependency file] **** │ │ fatal: [localhost]: FAILED! => { │ │ "changed": false, │ │ "rc": 1 │ │ } │ │ │ │ MSG: │ │ │ │ MODULE FAILURE │ │ See stdout/stderr for the exact error │ │ │ │ │ │ MODULE_STDERR: │ │ │ │ sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges? │ │ │ │ │ │ PLAY RECAP ***** │ │ localhost : ok=24 changed=0 unreachable=0 failed=1 skipped=26 rescued=0 ignored=0 │

My workaround will be to attempt to get a portable java deployed into the search heads

Hariprasath-3091 commented 6 months ago

@gjanders , we tried with search heads and we face the same error Can u share the steps which u performed for search heads ?

gjanders commented 6 months ago

@Hariprasath-3091 we uploaded an entire java JDK into the S3 bucket and had it deployed by the AppFramework

vivekr-splunk commented 1 month ago

@skirven4 please try the latest version of docker-splunk and SOK.