Update to Kubernetes 1.14.3
#72
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I am not sure why the diff says +100k lines, but the diff doesn't display them anywhere 🤔 |
|
|
|
@arianvp thanks! We're on |
f-f
changed the title
1.14.3
|
I guess we could add extracting the kube version as a build step for releases? |
|
@arianvp yes! It'd be lovely to automatically have it in the README (as we are templating the README already anyways..) |
|
LGTM. we can do that hackery later |
Modify Kubernetes generator to support more cases (#69) * Adjust dhall-kubernetes-generator to handle different swagger specs Remove defaults for lists
f-f
force-pushed
the
update-to-latest-kubernetes
branch
from
4b96d21
to
95c1fda
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This upgrades to the latest version of
nixpkgs-channels, which means that we get a newer version of the Kubernetes spec. It also includes some fixes to the nix workflow, that we figured it was slightly off in #70@arianvp do you know how to get which Kubernetes version we get for a given commit of
nixpkgs-channels?