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

[v0.4] gke 1.6.0 #258

Merged
merged 3 commits into from
Oct 18, 2024
Merged

Conversation

vardhaman22
Copy link
Contributor

@vardhaman22 vardhaman22 commented Oct 15, 2024

issue: rancher/rancher#47552

  • added gke 1.6.0
  • updated kube bench to 0.9.0
    Note: gke 1.2.0 is not removed since gke 1.6.0 is only for versions >=1.29 and other gke profiles are not available in upstream kube-bench and the minimum supported k8s version in rancher v2.8 is 1.25

@vardhaman22 vardhaman22 requested a review from a team as a code owner October 15, 2024 12:18
Copy link
Contributor

@andypitcher andypitcher left a comment

Choose a reason for hiding this comment

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

LGTM, could you just adjust the cfgs list within e2e:

dirs="ack-1.0 aks-1.0 cis-1.23 cis-1.24 cis-1.7 cis-1.8 config.yaml eks-1.0.1 eks-1.1.0 eks-1.2.0 eks-stig-kubernetes-v1r6 gke-1.0 gke-1.2.0 rh-0.7 rh-1.0"
? By adding gke 1.6.0.
We could have a separate PR to remove/add the cfgs for the given release.

This was referenced Oct 16, 2024
@vardhaman22
Copy link
Contributor Author

LGTM, could you just adjust the cfgs list within e2e:

dirs="ack-1.0 aks-1.0 cis-1.23 cis-1.24 cis-1.7 cis-1.8 config.yaml eks-1.0.1 eks-1.1.0 eks-1.2.0 eks-stig-kubernetes-v1r6 gke-1.0 gke-1.2.0 rh-0.7 rh-1.0"

? By adding gke 1.6.0.
We could have a separate PR to remove/add the cfgs for the given release.

done. And updated the PR description

@vardhaman22 vardhaman22 merged commit dc3f56d into rancher:release/v0.4 Oct 18, 2024
8 checks passed
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