Pod [support-k6-operator-controller-manager-6fff986c94-rc2ks] is in CrashLoopBackOff for the [4] time #501
Labels
bug
Something isn't working
Comments
|
doing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief summary
Logs from pod do not show any issues. I tried changing the image from
grafana/k6-operator:controller-v0.0.18tografana/k6-operator:latestand still not having any luckk6-operator version or image
v0.0.18
Helm chart version (if applicable)
3.10.1
TestRun / PrivateLoadZone YAML
none, just controller deployment for now is in crashloop
Other environment details (if applicable)
No response
Steps to reproduce the problem
installed helm chart into a custom namespace and the
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "2"
meta.helm.sh/release-name: support
meta.helm.sh/release-namespace: rc-e2e-api-49059
creationTimestamp: "2024-11-26T14:09:17Z"
generation: 2
labels:
app.kubernetes.io/component: controller
app.kubernetes.io/instance: support
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: k6-operator
app.kubernetes.io/part-of: k6-operator
app.kubernetes.io/version: 0.0.18
control-plane: controller-manager
helm.sh/chart: k6-operator-3.10.1
name: support-k6-operator-controller-manager
namespace: rc-e2e-api-49059
resourceVersion: "1174488240"
uid: 126b81ed-d466-4774-bb21-3f4febf7654f
spec:
progressDeadlineSeconds: 600
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
app.kubernetes.io/instance: support
app.kubernetes.io/name: k6-operator
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
app.kubernetes.io/instance: support
app.kubernetes.io/name: k6-operator
control-plane: controller-manager
spec:
containers:
- args:
- --metrics-addr=127.0.0.1:8080
command:
- /manager
image: ghcr.io/grafana/k6-operator:latest
imagePullPolicy: IfNotPresent
name: manager
resources:
limits:
cpu: 100m
memory: 100Mi
requests:
cpu: 100m
memory: 50Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
- args:
- --secure-listen-address=0.0.0.0:8443
- --upstream=http://127.0.0.1:8080/
- --logtostderr=true
- --v=10
image: gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0
imagePullPolicy: IfNotPresent
name: kube-rbac-proxy
ports:
- containerPort: 8443
name: https
protocol: TCP
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: k6-operator-controller
serviceAccountName: k6-operator-controller
terminationGracePeriodSeconds: 10
status:
conditions:
lastUpdateTime: "2024-11-26T14:14:55Z"
message: ReplicaSet "support-k6-operator-controller-manager-7fc9fdcdd5" has successfully
progressed.
reason: NewReplicaSetAvailable
status: "True"
type: Progressing
lastUpdateTime: "2024-11-26T14:20:47Z"
message: Deployment does not have minimum availability.
reason: MinimumReplicasUnavailable
status: "False"
type: Available
observedGeneration: 2
replicas: 1
unavailableReplicas: 1
updatedReplicas: 1
Expected behaviour
it keeps bouncing
kubectl events
Actual behaviour
does not stay stable
The text was updated successfully, but these errors were encountered: