Skip to content
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

Proposal: add info about non-namespaced resources in "how many clusters"-article #311

Open
tsaarni opened this issue May 25, 2020 · 1 comment

Comments

@tsaarni
Copy link

tsaarni commented May 25, 2020

Thank you for very informational and clearly written article https://learnk8s.io/how-many-clusters.

For the cons side of a large shared cluster, the article mentions cluster-wide services like DNS and shared resources like CPU and memory. I would like to propose mentioning also that certain Kubernetes resource kinds are not namespaced and therefore cannot be administered in isolation.

Example use case for custom resource definition (CRD) resource kind:

Two users are working in separate namespaces in a shared cluster. Users would like to deploy a particular version of operator "SampleDB". The operator requires installation of CRDs, which are not namespaced and therefore cannot be managed independently by the users working on the shared cluster. The deployment and version upgrades need to be done by the cluster administrator in coordination with the users.

@weibeld
Copy link
Collaborator

weibeld commented May 25, 2020

@tsaarni, thanks for the suggestions. This is definitely an important point that we missed. We will check and then attempt to include it in the article.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants