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

RFC: Add additional custom namespaces to k8s schema #3731

Closed
wants to merge 2 commits into from

Conversation

nemacysts
Copy link
Member

I see two potential solutions for allowing folks to use arbitrary namespaces:

  • we gatekeep them by needing us to add their namespace to this allowlist (which lets us make sure that they've correctly labeled their namespace as well as done everything else that we expect) OR,
  • we get rid of the allowlist and allow folks to put whatever namespace they'd like and expect that they know what they're doing :)

I see two potential solutions for allowing folks to use arbitrary
namespaces:
* we gatekeep them by needing us to add their namespace to this
  allowlist (which lets us make sure that they've correctly labeled
  their namespace as well as done everything else that we expect) OR,
* we get rid of the allowlist and allow folks to put whatever namespace
  they'd like and expect that they know what they're doing :)
@EmanElsaban
Copy link
Contributor

I think for now option 1 seems good because it's an exception but if we saw later more cases that require other ns then maybe we allow whatever ns?

@nemacysts
Copy link
Member Author

I would personally prefer the second option (getting rid of the allowlist) since it's less effort, but I'm not sure what everyone else thinks :)

@nemacysts
Copy link
Member Author

we'll go with #3732 instead :)

@nemacysts nemacysts closed this Oct 26, 2023
@nemacysts nemacysts deleted the luisp/allow-jenkins-namespace-usage branch November 15, 2024 18:46
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

Successfully merging this pull request may close these issues.

2 participants