Skip to content

Create an individual namespace for user to operate  #69

@jianh619

Description

@jianh619

What steps did you take and what happened:

User need provide config such as kubeconfig/pullsecret/product settings etc , and store it by either secret or configmap in a namespace . It's not suitable to just use crossplane install namespace crossplane-system for following reasons:

  • The crossplane installed namespace is different from OCP and k8s , gitops experience is un-consistent
  • All these config are user data , it should be protected by user themselves( it may be deleted when uninstalling gitops tools)

What did you expect to happen:

Create an individual namespace to user to operate , it may not have to customize by user itself .

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
  • Instana version:
  • Crossplane version:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions