Skip to content

CSPL-4707 Handle transient phase changes during app framework operations#1869

Draft
kasiakoziol wants to merge 10 commits into
developfrom
feature/CSPL-4707-flaky-m4-app-downgrade-phase
Draft

CSPL-4707 Handle transient phase changes during app framework operations#1869
kasiakoziol wants to merge 10 commits into
developfrom
feature/CSPL-4707-flaky-m4-app-downgrade-phase

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.

gabrielm-splunk and others added 10 commits April 16, 2026 14:32
Version 3.0.0 was inadvertently removed by automated PR (commit 1139fcf)
when 3.1.0 was added. Customers reported the version missing from
`helm search repo` results.

Changes:
- Restored 3.0.0 packaged chart from git tag
- Added 3.0.0 entries to docs/index.yaml for both splunk-enterprise and splunk-operator charts
- Chart digest: db5890e3bcc95f9ca7298873cc08b4a5d1ee86ccb4ad4e5334a0ab5d7a5fdb5e

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update index.yaml with correct SHA256 digests matching actual tarballs:
- splunk-enterprise-3.0.0: ae82f6c8edee4d827817fe6c9c6447c422a03c59595a0f6e779cef847a83b611
- splunk-operator-3.0.0: bd318b1f4022421a3fd429b186ca344c61d04a3c2bbdd5cc535d960773558e44

Resolves comment from vivekr-splunk on PR #1832

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit addresses four vulnerability findings from the container scanner:

- VULN-71179: Upgrade github.com/aws/aws-sdk-go-v2/service/s3 from v1.84.1 to v1.99.0
- VULN-71171: Upgrade go.opentelemetry.io/otel/sdk from v1.40.0 to v1.43.0
- VULN-71183: Upgrade github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream from v1.6.11 to v1.7.8
- VULN-71182: Upgrade Go stdlib from v1.25.8 to v1.26.2

All dependency updates meet or exceed the minimum versions required by the
container scanner. Unit tests pass with 83.6% composite coverage.

Jira: VULN-71179, VULN-71171, VULN-71183, VULN-71182

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Update Go version references in build configuration files to match
the go.mod update for VULN-71182 compliance.

Files updated:
- Dockerfile: golang:1.25.8 -> golang:1.26.2
- Dockerfile.distroless: golang:1.25.8 -> golang:1.26.2
- .env: GO_VERSION=1.25.8 -> GO_VERSION=1.26.2

GitHub Actions workflows automatically use GO_VERSION from .env,
so no workflow file changes are needed.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Introduce a feature gate registry backed by k8s.io/component-base/featuregate
so new capabilities can be gated behind --feature-gates=<Gate>=true|false with
Alpha/Beta/GA lifecycle. Migrate the validation webhook toggle from the
ENABLE_VALIDATION_WEBHOOK env var to a ValidationWebhook feature gate with
backwards-compatible env var support.

- Add pkg/config/featuregates.go registry with SetupFeatureGates and
  IsFeatureGateEnabled helpers, plus unit tests
- Wire feature gate flags into cmd/main.go and log effective gate states
  at startup
- Use os.LookupEnv for ENABLE_VALIDATION_WEBHOOK so the deprecation
  warning fires whenever the env var is set, not just when it equals "true"
- Update kustomization files with SPLUNK_GENERAL_TERMS value
- Add docs/FeatureGates.md with usage and instructions for adding new gates
- Update docs/ValidationWebhook.md with CLI-over-env-var precedence note
* Embed values

* Embed values

* Move fixtures

* Fix copyrights
Fix container scan vulnerabilities (VULN-71179, VULN-71171, VULN-71183, VULN-71182)
Restore helm chart version 3.0.0 to repository index
Add splunkOperator.featureGates map to values so operators can
enable feature gates via helm install/upgrade without per-gate
chart modifications. A helper template formats the map into a
single --feature-gates=Key1=true,Key2=false arg; the deployment
template conditionally includes it when the map is non-empty.

Also introduces helm-unittest with Makefile targets (helm-lint,
helm-test, helm-check) and fixes a pre-existing nindent bug in
the extraEnvs rendering.
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.

4 participants