-
Currently the `nginx.ingress.kubernetes.io/auth-tls-secret` annotation takes a single secret with a key named `ca.crt` (https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/…
hoeg updated
10 months ago
-
This tool is looking great, would you consider including the ability to use JIT credentials to avoid storing secrets to all the databases inside the application?
-
### TL;DR
When using multiple secrets in the secrets input for google-github-actions/deploy-cloudrun, additional `^,^` characters appear unexpectedly, preventing successful deployment.
### Expected …
-
### Specification
`touch` serves two purposes
1. Will create a new empty file if no file exists at that path.
2. Will update the timestamps of a file if it already exists.
For our `secrets tou…
-
### Specification
There are times when we need to transfer the secrets from a vault to either another vault or the user's file system. Sometimes, only one secret needs to be transferred. Other times,…
-
We've had multiple requests for ASO resources to have greater support for dynamic properties - #2950 being one example.
While we have good support for publishing dynamic values from Azure to Config…
-
### What happened?
A previous enhancement has added a warning event when a pull secret is missing: https://github.com/kubernetes/kubernetes/pull/117927
If the image has pulled successfully becau…
-
### Description
I am running a self-hosted instance of Gitea with two runners both setup as host (no Docker), one is on the same server as my Gitea instance, one is on another server. Both have ":ho…
-
### Problem Description
I would like to store secrets in omni which can be used as part of a cluster template, but not shared or exposed, only added when Omni compiles the template.
### Solution
S…
-
is it possible?