-
Notifications
You must be signed in to change notification settings - Fork 74
CCM namespace should be labelled as privileged #202
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
Conversation
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lobziik The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm I just tested this on OpenStack. It allows CCM to start and nodes become ready. |
|
Incidentally, OpenStack uses CCM by default so our CI is currently completely on fire. If we could merge this quickly I'd be very grateful. |
|
@mdbooth Did you review the openstack failures here? Looks like you'll need to fix the storage as well as the CCM, will get this merged soon but would like to see at least some of the CI pass/run |
Yes I did, and they're confusing because that namespace already has the correct labels. Lets handle that separately as that's a much smaller fire. |
Also, I just created a cluster using this PR. Although I see this error in the logs in my cluster, the pods deploy shortly thereafter 🤔 I wonder if there's a race between the namespace and deployment creation? They certainly seem to be created in order. |
|
/retest-required |
|
/retest |
|
appears to do no harm (some passes) and this has a good chance of unwedging us. m erging |
All techpreview jobs are currently failing because of the new pod security admission policy checks. This should resolve the issue for now