Skip to content

Conversation

kasiakoziol
Copy link
Collaborator

No description provided.

@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 13585981453

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.008%) to 86.581%

Totals Coverage Status
Change from base Build 13313195382: 0.008%
Covered Lines: 10543
Relevant Lines: 12177

💛 - Coveralls

@coveralls
Copy link
Collaborator

coveralls commented Feb 28, 2025

Pull Request Test Coverage Report for Build 13630576278

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.008%) to 86.585%

Files with Coverage Reduction New Missed Lines %
pkg/splunk/enterprise/cp.go 1 33.33%
Totals Coverage Status
Change from base Build 13589890322: -0.008%
Covered Lines: 10540
Relevant Lines: 12173

💛 - Coveralls

@kasiakoziol kasiakoziol force-pushed the feature/CSPL_3480_indexer_security_context_for_pvc branch from cad5bcc to 483e287 Compare March 3, 2025 12:10
More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
type: object
type: object
securityContext:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please schedule a meeting to review these changes? Any CRD changes should be thoroughly reviewed. For any feature or CRD changes, we require a Requirements Document or Design Document, which should be reviewed during the meeting before the PR is raised. We can create a spike to gather all the necessary requirements beforehand.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vivekr-splunk I raised it on our internal channel. It looks like we might not need this change any more. Based on the discussion, I will either follow your feedback or decline the PR.

@kasiakoziol kasiakoziol closed this Mar 5, 2025
@kasiakoziol
Copy link
Collaborator Author

kasiakoziol commented Mar 5, 2025

This is already implemented as described under #1416 comment section

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.

3 participants