Bumped k3s version to bring in updated HNS Network call. #1605
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
Signed-off-by: Jamie Phillips <jamie.phillips@suse.com>
brandond
approved these changes
Aug 10, 2021
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.
Signed-off-by: Jamie Phillips jamie.phillips@suse.com
Proposed Changes
The waitManagementIP function in pkg/daemons/agent/agent_windows.go is calling the incorrect HNS function. It is calling GetHNSEndpointByName instead of calling GetHNSNetworkByName.
k3s-io/k3s@dcf0657...ae909c7
Types of Changes
Bugfix
Verification
Deploy a Windows enabled cluster and a windows node. Check that the logs don't contain the following error message.
Linked Issues
Further Comments