You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have already searched this project's issues to determine if a bug report has already been made.
What happened?
unable to apply kube_policies due to error namespaces "node-image-cache" not found
Steps to Reproduce
Start bootstrapping guide
get to kyverno guide
attempt to apply the kube_policies module
Relevant log output
* Failed to execute "tofu apply -lock-timeout=30m -input=false"in ../../../../.terragrunt-cache/TQ4oD8TLViCMjdCi2aoNvpWoGjw/LLAAJNcpJ-3Xlv1YMiX0HdHm1T8/kube_policies
╷
│ Error: namespaces "node-image-cache" not found
│
│ with module.prepull_pod["amd64"].kubernetes_secret.secrets,
│ on ../kube_pod/main.tf line 438, in resource "kubernetes_secret""secrets":
│ 438: resource "kubernetes_secret""secrets" {
│
╵
╷
│ Error: namespaces "node-image-cache" not found
│
│ with module.prepull_pod["arm64"].kubernetes_secret.secrets,
│ on ../kube_pod/main.tf line 438, in resource "kubernetes_secret""secrets":
│ 438: resource "kubernetes_secret""secrets" {
│
╵
╷
│ Error: namespaces "node-image-cache" not found
│
│ with module.prepull_pod["amd64"].kubernetes_role.pod_reader,
│ on ../kube_pod/main.tf line 451, in resource "kubernetes_role""pod_reader":
│ 451: resource "kubernetes_role""pod_reader" {
│
╵
╷
│ Error: namespaces "node-image-cache" not found
│
│ with module.prepull_pod["arm64"].kubernetes_role.pod_reader,
│ on ../kube_pod/main.tf line 451, in resource "kubernetes_role""pod_reader":
│ 451: resource "kubernetes_role""pod_reader" {
│
╵
The text was updated successfully, but these errors were encountered:
uptownhr
changed the title
[Bug]: bootstrapping - namespaces "node-image-cache" not found
[Bug]: bootstrapping(kyverno) - namespaces "node-image-cache" not found
Jan 17, 2025
Prior Search
What happened?
unable to apply kube_policies due to error
namespaces "node-image-cache" not found
Steps to Reproduce
kube_policies
moduleRelevant log output
The text was updated successfully, but these errors were encountered: