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

Fix webhook certificates always being issued for the marblerun namespace when installing with CLI #573

Merged
merged 4 commits into from
Feb 1, 2024

Conversation

daniel-weisse
Copy link
Member

v1.4 introduced the --namespace flag, which allows users to interact with MarbleRun deployed to non-default Kubernetes namespaces.
This also allows users to install MarbleRun to different namespaces using just the CLI.
However, when creating the certificate used by MarbleRun's webhook, the DNS name was in all cases incorrectly issued for the marblerun namespace, instead of the namespace MarbleRun was being installed into.

Proposed changes

  • Fix the DNS name of the webhook certificate to always include the correct namespace
  • Automatically detect if cert-manager is installed in the cluster, and use it instead of self issuing certificates for the webhook
  • Add a warning about auto-injecto to the docs when installing multiple MarbleRun deployments in one cluster

Copy link

netlify bot commented Jan 31, 2024

Deploy Preview for marblerun-docs canceled.

Name Link
🔨 Latest commit 5613a17
🔍 Latest deploy log https://app.netlify.com/sites/marblerun-docs/deploys/65bb946c99e7f1000825d7ac

Signed-off-by: Daniel Weiße <dw@edgeless.systems>
Signed-off-by: Daniel Weiße <dw@edgeless.systems>
… to one cluster

Signed-off-by: Daniel Weiße <dw@edgeless.systems>
cli/internal/cmd/install.go Outdated Show resolved Hide resolved
Signed-off-by: Daniel Weiße <dw@edgeless.systems>
@daniel-weisse daniel-weisse merged commit c91b988 into master Feb 1, 2024
11 checks passed
@daniel-weisse daniel-weisse deleted the fix/cli/injector-namespace branch February 1, 2024 13:16
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