-
Notifications
You must be signed in to change notification settings - Fork 40k
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
federation: Adding secret API #29138
Conversation
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
4 similar comments
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
ok to test |
@nikhiljindal is back! :-) Could you take a look? @kshafiee could you please add an e2e test for this (i.e. one that creates, deletes and updates a secret, and confirms that it's appropriately reflected in the API). Let me know if you're unclear on how to do that. I can send you some pointers. |
ok to test |
@quinton-hoole would be great if you can send me the pointers on e2e test, thx |
@kshafiee You will also need to run hack/update-codegen.sh for it to update the generated clientset. |
a667131
to
dd1c55c
Compare
TestAdmissionNamespaceExists failure seems unrelated.
@k8s-bot unit test this issue: #IGNORE |
@nikhiljindal just rebased and added the e2e test file federated-secret.go |
} | ||
}) | ||
|
||
It("should succeed", func() { |
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.
change the first param to It to "should be created and deleted successfully".
Thanks @kshafiee the e2e test looks good barring few comments I have added. Also you seem to have deleted some files from clientset_generated that seems unintentional. Your code should not be compiling without those files (it is failing on jenkins). |
Also cc @kubernetes/sig-cluster-federation |
This PR resolves #29337 |
Thanks @nikhiljindal for your comments! |
cc @sig-cluster-federation |
Great to see the tests pass on Jenkins. Code changes LGTM barring one unresolved comment. Can you please fix that? Also please squash the commits. |
GCE e2e build/test failed for commit 262ae3d. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test passed for commit 262ae3d. |
Thanks @nikhiljindal for your comments!
|
Awesome, thanks LGTM |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 262ae3d. |
Automatic merge from submit-queue |
Adding secret API to federation-apiserver and updating the federation client to include secrets