CSPL-3964: Upgrading operator-sdk #1642
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gabrielm-splunk
requested review from
Igor-splunk,
kasiakoziol,
kubabuczak,
patrykw-splunk,
rlieberman-splunk and
vivekr-splunk
Collaborator
Pull Request Test Coverage Report for Build 20343950634Details
💛 - Coveralls |
gabrielm-splunk
force-pushed
the
CSPL-3964_Upgrade-operator-sdk
branch
from
8a01a85 to
b9cfd53
Compare
| - develop | ||
| - main | ||
| - feature** | ||
| - CSPL-3964_Upgrade-operator-sdk |
Collaborator
There was a problem hiding this comment.
Make sure to remove this line before merging.
Collaborator
There was a problem hiding this comment.
Will approve once this is removed. Looks good otherwise!
kubabuczak
requested changes
Dec 12, 2025
Collaborator
kubabuczak
left a comment
kubabuczak
left a comment
There was a problem hiding this comment.
Why didn't you apply changes listed in Operator SDK upgrade guides?
Collaborator
Author
@kubabuczak Everything should be addressed within this PR from all migrations. Not everything from those version docs are relevant for us (i.e. webhooks, linting, testing that we already have implementation for, etc) as was pointed out in the prior PR. Is there something specifically you expect to see from these migrations that aren't addressed? |
… as well as removing some uneccessary env vars added to the workflows.
gabrielm-splunk
force-pushed
the
CSPL-3964_Upgrade-operator-sdk
branch
from
b9cfd53 to
5fcc685
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Upgrading operator-sdk to version 1.41.1 and Golang version to 1.24.4. There were some linting changes that trickled through, but were very minor, so just decided to leave in. Thankfully, there weren't any breaking changes, so this was pretty straightforward other than some go mod changes (ran
go mod tidyto resolve). This will help resolve security vulnerability: https://splunk.atlassian.net/browse/VULN-42799Key Changes
The main updates are in the
.envandDockerfileTesting and Verification
Ran operator locally, installed operator on EKS cluster, and ran unit tests. Added this branch to be picked up by integration testing, so will monitor outputs of that.
Related Issues
PR Checklist