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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[YUNIKORN-1977] E2E test for verifying user info with non kube-admin user #915
[YUNIKORN-1977] E2E test for verifying user info with non kube-admin user #915
Changes from 4 commits
62be8c1
f4e55e3
9412297
334cbb0
4daafa0
f3b153a
45f5266
e567e1c
b265689
b2e717a
30954d5
735ceaf
a232066
2e25c0e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use
KubeCtl.CreateSecret()
if possible. If the annotation is necessary, create a new method with the nameCreateSecretWithAnnotation(secret *v1.Secret, namespace string, annotations map[string]string)
to avoid calling this directly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the code with requested changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We know the type of this object. It's
si.UserGroupInformation
, let's use that.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the code with requested changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of this should NOT be necessary. Way too complicated to mess around with separate
kubectl
calls.You can do this:
After this point,
kClient
will use the token for authentication there's no need to delete/restore anything.New method in
KubeCtl
:Also, try to retrieve the secret token using
KubeCtl
. We might need to create a new method for it, but again, it shouldn't involve running thekubectl
command:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure @pbacsko will accommodate the requested changes.