Open
Description
In my AKS cluster with kubernetes version v1.25.6 the reloader seems to be stuck in the starting controller state.
time="2023-07-31T15:18:54Z" level=info msg="Environment: Kubernetes"
time="2023-07-31T15:18:54Z" level=info msg="Starting Reloader"
time="2023-07-31T15:18:54Z" level=warning msg="KUBERNETES_NAMESPACE is unset, will detect changes in all namespaces."
time="2023-07-31T15:18:54Z" level=info msg="created controller for: configMaps"
time="2023-07-31T15:18:54Z" level=info msg="Starting Controller to watch resource type: configMaps"
time="2023-07-31T15:18:54Z" level=info msg="created controller for: secrets"
time="2023-07-31T15:18:54Z" level=info msg="Starting Controller to watch resource type: secrets"
However, the version v0.0.58
works fine
Helm Values
fullnameOverride: reloader
reloader:
deployment:
annotations:
checkov.io/skip2: CKV_K8S_38=Managed by reloader
replicas: 1
securityContext:
runAsNonRoot: true
runAsUser: 65534
seccompProfile:
type: RuntimeDefault
image:
name: ghcr.io/stakater/reloader
tag: v1.0.32
pullPolicy: Always
containerSecurityContext:
capabilities:
drop:
- ALL
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
resources:
limits:
cpu: "100m"
memory: "512Mi"
requests:
cpu: "10m"
memory: "128Mi"
readOnlyRootFileSystem: true
Metadata
Assignees
Labels
Type
Projects
Status
Todo
Activity