Skip to content

[Backport stable/2023.2] fix(valkey): create deployment namespace #4304

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.

Sign up for GitHub

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

Merged
atlas-by-vexxhost merged 1 commit into from
Aug 20, 2026
Merged

[Backport stable/2023.2] fix(valkey): create deployment namespace #4304

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions releasenotes/notes/valkey-create-namespace-eb0189a13c793180.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
fixes:
- |
The Valkey role now creates its configured deployment namespace before
creating certificate resources.
6 changes: 6 additions & 0 deletions roles/valkey/tasks/main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,15 @@
# SPDX-License-Identifier: Apache-2.0

- name: Create TLS resources
run_once: true
kubernetes.core.k8s:
state: present
definition:
- apiVersion: v1
kind: Namespace
metadata:
name: "{{ valkey_helm_release_namespace }}"

- apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
Expand Down
Loading