Skip to content

Update k8s version to 1.35#2403

Draft
za wants to merge 9 commits intoOWASP:masterfrom
za:issue-2357-upgrade-k8s-1.35
Draft

Update k8s version to 1.35#2403
za wants to merge 9 commits intoOWASP:masterfrom
za:issue-2357-upgrade-k8s-1.35

Conversation

@za
Copy link
Contributor

@za za commented Feb 26, 2026

Issue: #2357

What kind of changes does this PR include?

  • Fixes or refactors
  • A new challenge
  • Additional documentation
  • Something else

Description

Upgrade k8s version to 1.35

Relations

#2357

References

Checklist:

  • All the contributions made are solely the work of me and my co-authors
  • I used AI to generate parts of the content.
  • I tested the changes in this PR (if applicable)
  • I added unit tests to ensure my change works (when change in Java or on front-end code)
  • I added UI tests to ensure my UI changes work (when change in the overall UI, not needed if just adding a challenge)
  • The PR passes pre-commit hooks and automated tests

@za
Copy link
Contributor Author

za commented Feb 26, 2026

All tests have passed @commjoen kindly check.

@za za mentioned this pull request Feb 26, 2026
@commjoen
Copy link
Collaborator

Thank you @za hope to do some tests myself soon :)

@za
Copy link
Contributor Author

za commented Feb 26, 2026

Take your time @commjoen Are you referring to manual tests?

@commjoen
Copy link
Collaborator

There are a few files missing an update, can you fix those please?
image

as suggested by @commjoen
OWASP#2403 (comment)

Previously, it wasn't updated yet
@za
Copy link
Contributor Author

za commented Feb 27, 2026

Hi @commjoen PR updated. Kindly check.

@za
Copy link
Contributor Author

za commented Feb 27, 2026

I wonder why the github action on dead link checker is failing @commjoen ?

@za
Copy link
Contributor Author

za commented Feb 27, 2026

All checks passed now, after I merge latest master cc: @commjoen

@commjoen
Copy link
Collaborator

commjoen commented Mar 1, 2026

will start checking now :)

@commjoen
Copy link
Collaborator

commjoen commented Mar 1, 2026

Have you run the terratests? it looks like tf init no longer works due to different aws modules (will fix this in another branch)

@za
Copy link
Contributor Author

za commented Mar 2, 2026

Have you run the terratests? it looks like tf init no longer works due to different aws modules (will fix this in another branch)

No, I haven't. I need to update my cloud billing first 😺

@commjoen commjoen marked this pull request as draft March 2, 2026 08:56
@za
Copy link
Contributor Author

za commented Mar 2, 2026

Hi @commjoen , the terratest is failing. Should I make the changes in this PR or a separate one?

➜  aws git:(issue-2357-upgrade-k8s-1.35) ✗ go test -timeout 99999s 

<snipped>

TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: - Installed hashicorp/null v3.2.2 (signed by HashiCorp)
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: ╷
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ Error: Failed to query available provider packages
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ Could not retrieve the list of available versions for provider    
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ hashicorp/aws: locked provider registry.terraform.io/hashicorp/aws 6.26.0
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ does not match configured version constraint >= 6.0.0, >= 6.23.0, ~>
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ 6.26.0, >= 6.28.0; must use terraform init -upgrade to allow selection of
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ new versions
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ To see which modules are currently depending on hashicorp/aws and what
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ versions are specified, run the following command:
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │   

@commjoen
Copy link
Collaborator

commjoen commented Mar 2, 2026

Hi @commjoen , the terratest is failing. Should I make the changes in this PR or a separate one?

➜  aws git:(issue-2357-upgrade-k8s-1.35) ✗ go test -timeout 99999s 

<snipped>

TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: - Installed hashicorp/null v3.2.2 (signed by HashiCorp)
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: ╷
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ Error: Failed to query available provider packages
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ Could not retrieve the list of available versions for provider    
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ hashicorp/aws: locked provider registry.terraform.io/hashicorp/aws 6.26.0
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ does not match configured version constraint >= 6.0.0, >= 6.23.0, ~>
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ 6.26.0, >= 6.28.0; must use terraform init -upgrade to allow selection of
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ new versions
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ To see which modules are currently depending on hashicorp/aws and what
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │ versions are specified, run the following command:
TestTerraformWrongSecretsAWS 2026-03-02T16:08:02+07:00 logger.go:67: │   

please import master, that should fix a lot already, then feel free to udpate whatever is necessary in this branch :) .

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.

2 participants