-
Notifications
You must be signed in to change notification settings - Fork 56
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
Cherry-pick minor fixes from open PRs #960
Conversation
As of Kubernetes 1.24, serviceaccounttoken secrets are no longer created by default, and so this method cannot be used to login as the workspace serviceaccount when running locally. Instead, it's possible to use kubectl create token <sa-name> -n <namespace> to get the token used for the serviceaccount. Signed-off-by: Angel Misevski <[email protected]>
Recent versions of Kubernetes do not automatically mount image pull secrets to serviceaccounts, meaning that most workspace starts idle for 5 seconds waiting for something that is not going to happen. Instead we scope the check for waiting for image pull secrets to only be performed when running on OpenShift. On OpenShift, there is a race between the controller and the cluster API, where sometimes DWO creates a deployment that is immediately updated with image pull secrets, slowing workspace start due to the workspace pod needing to terminate. Signed-off-by: Angel Misevski <[email protected]>
Codecov ReportBase: 49.43% // Head: 49.43% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #960 +/- ##
=======================================
Coverage 49.43% 49.43%
=======================================
Files 38 38
Lines 2405 2405
=======================================
Hits 1189 1189
Misses 1093 1093
Partials 123 123 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Looks good to me. Tested running the controller locally on minikube v1.27.1 & kubernetes v1.24.1 & started the theia-next
sample workspace
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amisevsk, AObuchow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What does this PR do?
Cherry-picks two quality-of-life improvements from open PRs in order to merge them sooner:
make run
/make debug
when running on Kubernetes >=1.24).What issues does this PR fix or reference?
N/A
Is it tested? How?
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-path
to trigger)v8-devworkspace-operator-e2e
: DevWorkspace e2e testv8-che-happy-path
: Happy path for verification integration with Che