Skip to content

Feature/cspl 4378 test timeouts#1822

Draft
kasiakoziol wants to merge 26 commits intofeature/test-refactoringfrom
feature/CSPL-4378-test-timeouts
Draft

Feature/cspl 4378 test timeouts#1822
kasiakoziol wants to merge 26 commits intofeature/test-refactoringfrom
feature/CSPL-4378-test-timeouts

Conversation

@kasiakoziol
Copy link
Copy Markdown
Collaborator

Description

What does this PR have in it?

Key Changes

Highlight the updates in specific files

Testing and Verification

How did you test these changes? What automated tests are added?

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

  • Code changes adhere to the project's coding standards.
  • Relevant unit and integration tests are included.
  • Documentation has been updated accordingly.
  • All tests pass locally.
  • The PR description follows the project's guidelines.

minjieqiu and others added 20 commits March 12, 2026 16:45
CSPL-4186: Support splunk secret and make it available to Ansible via mount
Add a GitHub Actions workflow and supporting scripts for flaky test
analysis. Users can trigger the workflow manually with configurable
date ranges, branch filters, and reporting parameters.
- GitHub Actions workflow with workflow_dispatch trigger for on-demand
  flaky test analysis
- Bash script to download JUnit XML artifacts and run flaky test
  detection
- Python script to generate Markdown test failure statistics from
  JUnit reports
- Custom Matplotlib configuration for readable heatmap generation
- Dynamic artifact naming based on analysis date range
- .gitignore entry for generated JUnit report directories
…ws for ARM and Distroless builds to ensure failures are properly reported. (#1742)
…itattributes (#1767)

- Introduced .gitattributes to mark generated files for better handling in version control.
- Enhanced the build-test-push workflow by adding a new job to check for uncommitted changes after code generation, ensuring generated files are up to date before proceeding with the build.
* Add validation webhook for appRepo fields

- Add appsRepoPollInterval validation:
  - Default: 0 (disabled)
  - Minimum: 0, Maximum: 86400 (1 day)
  - Values between 1-59 are rejected (must be 0 or >= 60)

- Add appSources uniqueness validation:
  - Location + Scope combination must be unique across appSources
  - Uses defaults.scope when scope is not specified in appSource
  - volumeName is NOT part of uniqueness check

- Add unit tests for all new validations

* Add premiumAppsProps validation for appSources

- Validate that premiumAppsProps.type is required when scope is 'premiumApps'
- Check both source-level and defaults-level premiumAppsProps.type
- Add unit tests for premiumAppsProps validation scenarios

* Add extraEnv uniqueness validation

- Validate that environment variable names in spec.extraEnv are unique
- Report duplicate names with reference to the first occurrence
- Add unit tests for extraEnv uniqueness validation

* Add imagePullSecrets uniqueness validation

- Validate that secret names in spec.imagePullSecrets are unique
- Report duplicate names with reference to the first occurrence
- Add unit tests for imagePullSecrets uniqueness validation

* Add probe fields validation

- Validate livenessProbe, readinessProbe, and startupProbe configurations
- initialDelaySeconds: minimum 0
- timeoutSeconds: minimum 1
- periodSeconds: minimum 1
- failureThreshold: minimum 1
- Add unit tests for probe validation scenarios

* Add resource requirements validation

- Validate that memory request does not exceed memory limit
- Validate that cpu request does not exceed cpu limit
- Add unit tests for resource requirements validation

* Add SmartStore validation for volumes and indexes

- Validate that indexes require at least one volume to be configured
- Validate that index volumeName references an existing volume in volumes list
- Validate that index has volumeName or defaults.volumeName provided
- Update and add unit tests for SmartStore validation

* Add StorageClassSpec ephemeralStorage mutual exclusivity validation

- Validate that ephemeralStorage is mutually exclusive with storageClassName
- Validate that ephemeralStorage is mutually exclusive with storageCapacity
- Add unit tests for ephemeralStorage mutual exclusivity scenarios

* feat(validation): add imagePullSecrets existence validation

- Add ValidationContext to carry Kubernetes client for resource lookups
- Extend Validator interface with context-aware validation methods
- Implement ValidateImagePullSecretsExistence to verify secrets exist
- Update all CRD validators with context-aware validation functions
- Pass manager client to webhook server for API access
- Update ValidationWebhook.md documentation with new validation rules
- Add unit tests for imagePullSecrets existence validation

This enables the webhook to reject CRs that reference non-existent
secrets in spec.imagePullSecrets, providing early feedback to users.

---------

Co-authored-by: Patryk Wasielewski <pwasiele@splunk.com>
* Update Splunk Enterprise version from 10.0.0 to 10.2.0

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* add id-token: write to permissions

* add COSIGN_DOCKER_MEDIA_TYPES to signing steps

* use --recursive for signing distroless image

* remove --recursive from cosign verify

* cleanup

* add --recursive for standard image

---------

Co-authored-by: Gabriel J Mendoza <gabrielm@splunk.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Reset telemetry test to true after release
…using Splunk Operator for Kubernetes (#1604)

* federated search setup doc

* docs: address federated search review feedback

* docs: add federated search architecture diagram

* docs: clarify federated search scope
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants