This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
initContainers not working #1345
Labels
Comments
I've tested this and in my case the containers are not getting updated at all if there is a init container present. Deployment: apiVersion: apps/v1
kind: Deployment
metadata:
name: podinfo
namespace: default
annotations:
flux.weave.works/automated: "true"
flux.weave.works/tag.podinfod: semver:~1.0
spec:
replicas: 1
selector:
matchLabels:
app: podinfo
template:
metadata:
labels:
app: podinfo
annotations:
prometheus.io/scrape: 'true'
spec:
initContainers:
- name: init
image: quay.io/stefanprodan/podinfo:1.0.0
command:
- ./podinfo
- --version
containers:
- name: podinfod
image: quay.io/stefanprodan/podinfo:1.0.0
command:
- ./podinfo
- --port=9898
ports:
- name: http
containerPort: 9898
protocol: TCP Flux logs:
|
I have reproduced this locally by adding an initContainer in a YAML in my fork of flux-example. Also suspicious: it's not fetching image metadata for the initContainer:
|
Found it: https://github.com/weaveworks/flux/blame/master/cluster/kubernetes/resource/spec.go#L46 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Init pods are not updated but normal containers are.
Fluxctl result
Test deployment.
The text was updated successfully, but these errors were encountered: