Fix adapter connectivity in k8s #44
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
Signed-off-by: Utkarsh Srivastava <srivastavautkarsh8097@gmail.com>
leecalcote
approved these changes
May 5, 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: Utkarsh Srivastava srivastavautkarsh8097@gmail.com
Description
This PR fixes adapter connectivity issue when adapter is deployed inside k8s cluster.
Only validation of received kubeconfig is received in case adapter receives an empty kubeconfig and the deployment is within the cluster.
Adapter will automatically read the incluster config in the later stages hence fixing the broken communication.
Tested On:
KinD cluster
Notes for Reviewers
Signed commits