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

Configure release channel when creating GKE clusters #1260

Merged
merged 1 commit into from
Oct 15, 2019

Conversation

modular-magician
Copy link
Collaborator

@modular-magician modular-magician commented Oct 14, 2019

Original Author: @chrissng

`container`: Allow the configuration of release channels when creating GKE clusters.

"channel": c.Channel,
})
} else {
// Explicitly set the network policy to the default.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not a "network policy", so this comment can be updated.

Why do we want to explicitly set the channel to UNSPECIFIED if it is not returned by the API? Typically there is a difference between receiving a value like UNSPECIFIED and not receiving anything at all, but we would lose that in this case

Copy link
Contributor

Choose a reason for hiding this comment

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

In this case, when release channel is set to UNSPECIFIED, the GKE API returns a nil containerBeta.ReleaseChannel. As such, I had to make the assumption that the returned nil object refers to the UNSPECIFIED channel.

I would add an additional test to test for invalid channels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants