Skip to content

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

@tsaarni

Description

@tsaarni

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions