Add ServiceAccounts for kube-scheduler and kube-apiserver, remove default #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dghubble
changed the title
* Switch kube-scheduler from using the kube-system default ServiceAccount (with cluster-admin) to using a kube-scheduler ServiceAccount bound to the builtin system:kube-scheduler and system:volume-scheduler (required for StorageClass) ClusterRoles * https://kubernetes.io/docs/reference/access-authn-authz/rbac/#core-component-roles
* Switch kube-apiserver from using the kube-system default ServicAccount (with cluster-admin) to using a kube-apiserver ServiceAccount bound to cluster-admin (as before) * Remove the default-sa ClusterRoleBinding that allowed kube-apiserver and kube-scheduler (or other 3rd-party components added to kube-system) to use the kube-system default ServiceAccount for cluster-admin * Require all future components in kube-system define their own ServiceAccount
dghubble
force-pushed
the
always-use-service-accounts
branch
from
e0d124c
to
f382415
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Require all components in kube-system define their own ServiceAccount, the default kube-system ServiceAccount is no longer bound.
kube-schedulerServiceAccount and ClusterRoleBindingkube-schedulerfrom using thekube-systemdefault service account (with cluster-admin) to using a kube-scheduler ServiceAccount bound to the builtinsystem:kube-schedulerandsystem:volume-scheduler(required for StorageClass) ClusterRoleskube-apiserverServiceAccount and ClusterRoleBindingkube-apiserverfrom using the kube-system default service account (with cluster-admin) to using a kube-apiserver ServiceAccount bound the the cluster-admin ClusterRole (as before)default-saClusterRoleBinding that allowed kube-apiserver and kube-scheduler (or other 3rd-party components added to kube-system) to use thekube-systemdefaultServiceAccount for cluster-admin