fix: 🐛 don't ignore user token when testing cluster deployment mode #1264
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
mathieulaude
force-pushed
the
fix/kubeconfig-token
branch
from
fce3f84
to
cc488c3
Compare
Analysis Details0 Issues
Coverage and Duplications
Project ID: cloud-pi-native_console_AYsa46O31ebDtzs-pYyZ |
1 similar comment
Analysis Details0 Issues
Coverage and Duplications
Project ID: cloud-pi-native_console_AYsa46O31ebDtzs-pYyZ |
ArnaudTA
approved these changes
Jul 15, 2024
this-is-tobi
approved these changes
Jul 15, 2024
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.
Issues liées
Issues numéro:
Quel est le comportement actuel ?
Un kubeconfig en mode user token est considéré comme un cluster inaccessible.
Quel est le nouveau comportement ?
Le kubeconfig avec token est bien utilisé pour communiquer avec le cluster.
Cette PR introduit-elle un breaking change ?
Autres informations