Skip to content

Namespace prefix for multi-tenancy support #273

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

nihussmann
Copy link
Contributor

No description provided.

@nihussmann nihussmann changed the title Feature/prefix Namespace prefix vor multi-tenancy support Apr 11, 2025
@schnatterer schnatterer changed the title Namespace prefix vor multi-tenancy support Namespace prefix for multi-tenancy support Apr 11, 2025
@nihussmann nihussmann marked this pull request as draft April 11, 2025 13:39
@nihussmann nihussmann force-pushed the feature/prefix branch 3 times, most recently from f3b735f to 47e657b Compare April 24, 2025 11:46
String url = config.registry.proxyUrl ?: config.registry.url
String user = config.registry.proxyUsername ?: config.registry.readOnlyUsername ?: config.registry.username
String password = config.registry.proxyPassword ?: config.registry.readOnlyPassword ?: config.registry.password

k8sClient.createNamespace(namespace)
k8sClient.createNamespace(this.namespace)
k8sClient.createImagePullSecret('proxy-registry', namespace, url, user, password)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if "this" is neccessary for usage this.namespace, it should be used here, too.

Suggested change
k8sClient.createImagePullSecret('proxy-registry', namespace, url, user, password)
k8sClient.createImagePullSecret('proxy-registry', this.namespace, url, user, password)

@nihussmann nihussmann force-pushed the feature/prefix branch 6 times, most recently from 83318d3 to 67725d0 Compare April 25, 2025 13:36
@nihussmann nihussmann marked this pull request as ready for review April 25, 2025 14:24
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