RBAC Reference
kubernetes Instances Configuration
GCP
NUMBER OF NODE-SIZE | INSTANCE TYPE | CPU | MEMORY |
---|---|---|---|
1-5 | n1-standard-1 | 1 | |
6-10 | n1-standard-2 | 2 | |
11-100 | n1-standard-4 | 4 | |
101-250 | n1-standard-8 | 8 | |
251-500 | n1-standard-16 | 16 | |
more than 500 | n1-standard-32 | 32 |
AWS
NUMBER OF NODE_SIZE | INSTANCE TYPE | CPU | MEMORY |
---|---|---|---|
1-5 | m3.medium | 1 | 3.75 |
6-10 | m3.large | 2 | 7.50 |
11-100 | m3.xlarge | 4 | 15 |
101-250 | m3.2xlarge | 8 | 30 |
251-500 | c4.4xlarge | 8 | 30 |
more than 500 | c4.8xlarge | 16 | 60 |
api groups and resources
apiGroup | Resources |
---|---|
apps | daemonsets, deployments, deployments/rollback, deployments/scale, replicasets, replicasets/scale, statefulsets, statefulsets/scale |
core | configmaps, endpoints, persistentvolumeclaims, replicationcontrollers, replicationcontrollers/scale, secrets, serviceaccounts, services,services/proxy |
autoscaling | horizontalpodautoscalers |
batch | cronjobs, jobs |
policy | poddisruptionbudgets |
networking.k8s.io | networkpolicies |
authorization.k8s.io | localsubjectaccessreviews |
rbac.authorization.k8s.io | rolebindings,roles |
extensions | deprecated (read notes) |
Notes
In addition to the above apiGroups, you may see extensions being used in some example code snippets. Please note that extensions was initially created as a experiement and is been deprecated, by moving most of the matured apis to one of the groups mentioned above. You could read this comment and the thread to get clarity on this.