ServiceAccounts combined with Roles and RoleBindings are an essential component for continuous deployment or any other process that needs to communicate with Kubernetes. The alternative is to run an unsecured cluster which is not an option for any but smallest organizations. RBAC is required when more than one person is operating or using a cluster. If RBAC is enabled, ServiceAccounts are a must. We'll use them a lot in the chapters that follow.
Please consult the APIs that follow for any additional information about ServiceAccounts and related resources.
- ServiceAccount v1 core (https://v1-9.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#serviceaccount-v1-core)
- Role v1 rbac (https://v1-9.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#role-v1-rbac)
- ClusterRole v1 rbac (https://v1-9.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#clusterrole-v1-rbac)
- RoleBinding v1 rbac (https://v1-9.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#rolebinding-v1-rbac)
- ClusterRoleBinding v1 rbac (https://v1-9.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#clusterrolebinding-v1-rbac)
One more thing before you leave. Please consult jenkins-kubernetes-plugin (https://github.com/jenkinsci/kubernetes-plugin) for more information about the plugin.