Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add rancher-webhook-0.6 stream #37485

Merged
merged 2 commits into from
Dec 23, 2024

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 18, 2024

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. labels Dec 18, 2024
Copy link
Contributor Author

octo-sts bot commented Dec 18, 2024

Gen AI suggestions to solve the build error:

• Detected Error:

undefined: genericfeatures.StrictCostEnforcementForVAP
undefined: genericfeatures.StrictCostEnforcementForWebhooks

• Error Category: Dependency/Version

• Failure Point: Go build step failing due to incompatible Kubernetes dependency version

• Root Cause Analysis: The error occurs because we're trying to use k8s.io/kubernetes v1.30.3 which has features that aren't available in the current dependency chain. These feature flags were likely introduced in a newer version of the genericfeatures package.

• Suggested Fix:

  1. Modify the go/bump step in the melange YAML to use a compatible Kubernetes version:
  - uses: go/bump
    with:
      deps: k8s.io/kubernetes@v1.29.0 golang.org/x/crypto@v0.31.0
      modroot: .

• Explanation:
The error indicates missing feature flags that were likely introduced in Kubernetes 1.30+. Since v1.30.3 is still in alpha/beta, we should use the latest stable version (1.29.x) which will have a more stable API surface.

• Additional Notes:

  • Kubernetes 1.30 is currently in development/alpha stage
  • The StrictCostEnforcementForVAP and StrictCostEnforcementForWebhooks features are new additions
  • Rancher webhook may not be ready for k8s 1.30 features yet
  • Consider checking the go.mod in the upstream repository for their tested k8s version

• References:

The fix aligns with Wolfi's principles by:

  • Maintaining stability by using released versions
  • Ensuring security by using recent stable releases
  • Following upstream compatibility requirements

@Dentrax Dentrax changed the title rancher-webhook-0.5/0.5.5 package update add rancher-webhook-0.6 Dec 22, 2024
wolfi-bot and others added 2 commits December 23, 2024 00:27
Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
Signed-off-by: Dentrax <furkan.turkal@chainguard.dev>
@Dentrax Dentrax force-pushed the wolfictl-5cffc812-989b-458c-ba66-b9ade03ebd43 branch from 16f7e00 to a6b126b Compare December 22, 2024 21:28
@Dentrax Dentrax changed the title add rancher-webhook-0.6 add rancher-webhook-0.6 stream Dec 22, 2024
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 22, 2024
@Dentrax Dentrax enabled auto-merge (squash) December 22, 2024 21:33
@Dentrax Dentrax merged commit 0fef27b into main Dec 23, 2024
20 checks passed
@Dentrax Dentrax deleted the wolfictl-5cffc812-989b-458c-ba66-b9ade03ebd43 branch December 23, 2024 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants