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

Address common questions/needs regards to not create/use the ns scaffolded by the tool #1762

Closed
camilamacedo86 opened this issue Oct 30, 2020 · 2 comments
Labels
triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@camilamacedo86
Copy link
Member

camilamacedo86 commented Oct 30, 2020

What do you want to happen?

This issue was raised for we find the best way to address the common questions and requests:

  • How to deploy the operator in another NS? How to not let the tool create a new ns for my operator?
  • I'd like to run make deploy and get the project deployed in a specific namespaced informed instead of creating a new one.
  • I'd like the tool to help me to use a pre-existent namespace instead of creating a new one specifically for the operator.

Possible Solution

  • Add a flag option to the init command to define if the specific ns should or not be created to the project
  • Store this flag in the PROJECT file
  • And then, we might be able to use the EditPlugin to provide a feature to change the scaffolds to use the ns specified and no longer create the new ns by having an attribute in the PROJECT file.

Also, another option can be able to address these common requests via docs by explaining how users can customize their project to achieve it. See that we can cd config/default/ && kustomize edit set namespace "memcached-operator" && cd ../.. to deploy the project in another ns. However, I think it will create a new ns.

PS.: I already so this questions in the SDK issues as well and it came in as a result of a survey.

@camilamacedo86 camilamacedo86 added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 30, 2020
@camilamacedo86 camilamacedo86 changed the title Address common questions/needs regards ns created/used to deploy the operator Address common questions/needs regards to not create/use the ns scaffolded by the tool Oct 30, 2020
@camilamacedo86 camilamacedo86 removed the kind/feature Categorizes issue or PR as related to a new feature. label Nov 2, 2020
@camilamacedo86
Copy link
Member Author

/needs-triage

@camilamacedo86 camilamacedo86 added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Dec 1, 2020
@camilamacedo86
Copy link
Member Author

camilamacedo86 commented Dec 1, 2020

It will be solved by the config EP that has been done by @pwittrock. So, we are closing this one.
More info: #1831

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

1 participant