Release 0.8.1 #683
Merged
Release 0.8.1 #683
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
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wongma7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
|
/lgtm |
k8s-ci-robot
added
the
lgtm
k8s-ci-robot
removed
the
lgtm
Pull Request Test Coverage Report for Build 1437
💛 - Coveralls |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
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.
Is this a bug fix or adding new feature? new
What is this PR about? / Why do we need it? Need a new release for multiarchness since v0.8.0 mutliarch is broken: #656
What testing is done? 0.8.1 has the same tag as 0.8.1-rc.0 which I tested for multiarchness following the same steps as in #666
TODO: I will need to cherry-pick the kustomize changes into the release-0.8 branch.
Known issue:
Since I already tagged v0.8.1 before updating the Makefile in this PR, the "version" output in the v0.8.1 image is still going to show v0.8.0. In future, this PR should come first THEN it should be tagged, even if it means YAMLS will refer to images that haven't been pushed it.