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

fix: use provided k8s version even when a release channel is specified #1400

Closed

Conversation

jamiezieziula
Copy link

Related to #1279 & #1356 - this aims to allow users to define both a release channel to use as well as a defined version of kubernetes.

Copy link
Member

@bharathkkb bharathkkb left a comment

Choose a reason for hiding this comment

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

Thanks for the PR @jamiezieziula Can we append to an existing test to make sure this is WAI.

seenms like a good candidate.
it "has expected explicit version" do
expect(data['currentMasterVersion']).to eq explicit_version
expect(data['currentNodeVersion']).to eq explicit_version
end
is an example where we test the expected explicit version.

@jamiezieziula
Copy link
Author

@bharathkkb done!

@bharathkkb
Copy link
Member

Hi @jamiezieziula I am seeing an error where builds are failing with

  module.this.module.gke.google_container_cluster.primary: Still creating... [5m30s elapsed]
       ╷
       │ Error: Error waiting for creating GKE cluster: Failed to create cluster

Did setting both min_master_version and release_channel work in your environment? I did some investigation and it seemed like there was a previous issue #383 which we then added this conditional as a fix.

@comment-bot-dev
Copy link

@jamiezieziula
Thanks for the PR! 🚀
✅ Lint checks have passed.

@github-actions
Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Dec 20, 2022
@github-actions github-actions bot closed this Dec 27, 2022
@kespineira
Copy link

Hello! Was there any reason that this PR was not continued with?

@emonisme
Copy link

any update on this PR?

@apeabody apeabody reopened this Feb 10, 2023
@apeabody apeabody requested a review from ericyz as a code owner February 10, 2023 16:03
@apeabody
Copy link
Contributor

/gcbrun

@github-actions github-actions bot removed the Stale label Feb 10, 2023
@apeabody apeabody changed the title Use provided k8s version even when a release channel is specified fix: use provided k8s version even when a release channel is specified Apr 7, 2023
@apeabody
Copy link
Contributor

apeabody commented Apr 7, 2023

/gcbrun

@github-actions
Copy link

github-actions bot commented Jun 6, 2023

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Jun 6, 2023
@github-actions github-actions bot closed this Jun 14, 2023
@apeabody apeabody removed the Stale label Jun 14, 2023
@apeabody apeabody reopened this Jun 14, 2023
@github-actions
Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Aug 14, 2023
@github-actions github-actions bot closed this Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants