-
Notifications
You must be signed in to change notification settings - Fork 984
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
Add allow_privilege_escalation to container security contexts attributes #249
Add allow_privilege_escalation to container security contexts attributes #249
Conversation
Failing acceptance tests:
Somehow, the new fields are not properly updated, on it... |
Oh, Removing it for now... Saved those changes at https://github.com/pdecat/terraform-provider-kubernetes/tree/f-add-security-context-run_as_group |
97d6245
to
a0693bc
Compare
Updated so that For reference: IMO, the reference and design docs are not really explicit about that:
cf. https://v1-10.docs.kubernetes.io/docs/tasks/configure-pod-container/security-context/ This change allows the acceptance to pass while they used to fail when this attribute is not defined but |
Acceptance test results on GKE 1.11.4-gke.8 :
|
…, update documentation and acceptance tests
0f64089
to
1f80aef
Compare
Rebased on master. |
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.
Very nicely done! Thanks for quoting the references so exhaustively.
I've run this in internal CI and all is green, so we should be good here.
LGTM
I believe that |
@pdecat Is there any chance I could talk you into resurrecting your |
This adds the following attributes to container security context:
allow_privilege_escalation
(alpha since 1.10)run_as_group
And those to pod security context:
(alpha since 1.10)run_as_group
Re-ordered fields alphabetically to match reference docs:
Added the completely missing Container SecurityContext docs.
Note: this is based on #248 to fix
Deployment
acceptance tests before any code changes.TODO:
Resolves #247