Closed ManuelDittmar closed 11 months ago
jessesimpson36
commented
1 year ago We learned that some of our indentations were off in 8.3.1. Since your warnings mentions "limits" and "requests", I feel like it's because of the same issue. We fixed it in this PR #105 which is not yet released.
matt-gnu
commented
1 year ago Hi @jessesimpson36,
I assume, you did mot mean #105 which is from 2022, but #1013 which is current. Just stating this here for other readers hit by this bug.
We also got hit by this error when deploying 8.3.1, because in ArgoCD the application deployment will never reach a steady state, but will stay "out of sync", since the actual state (without resource limits) deviates from the specified state.
noizo
commented
1 year ago Also facing same issue in latest 8.3.1 helm.
When i run:
helm template camunda-devops-test camunda/camunda-platform -f values.yaml > camunda.yaml
and then
kubectl apply -f camunda.yaml
helm install won't work as well.
i'm getting this error:
error: error validating "camunda.yaml": error validating data: [ValidationError(Deployment.spec.template.spec.containers[0]): unknown field "limits" in io.k8s.api.core.v1.Container, ValidationError(Deployment.spec.template.spec.containers[0]): unknown field "requests" in io.k8s.api.core.v1.Container]; if you choose to ignore these errors, turn validation off with --validate=false
My tasklist definition looks like this:
tasklist:
resources:
requests:
cpu: 400m
memory: 1Gi
limits:
cpu: 1000m
memory: 2GiThat is how it's templating for me:
# Source: camunda-platform/templates/tasklist/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: camunda-devops-test-tasklist
labels:
app: camunda-platform
app.kubernetes.io/name: camunda-platform
app.kubernetes.io/instance: camunda-devops-test
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/part-of: camunda-platform
helm.sh/chart: camunda-platform-8.3.1
app.kubernetes.io/version: "8.3.1"
app.kubernetes.io/component: tasklist
annotations:
{}
spec:
replicas: 1
selector:
matchLabels:
app: camunda-platform
app.kubernetes.io/name: camunda-platform
app.kubernetes.io/instance: camunda-devops-test
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/part-of: camunda-platform
app.kubernetes.io/component: tasklist
template:
metadata:
labels:
app: camunda-platform
app.kubernetes.io/name: camunda-platform
app.kubernetes.io/instance: camunda-devops-test
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/part-of: camunda-platform
helm.sh/chart: camunda-platform-8.3.1
app.kubernetes.io/version: "8.3.1"
app.kubernetes.io/component: tasklist
annotations:
checksum/config: 01fde189e6ce2d18ab0e4c6231ef295e627a14e6df6769736dfccd4d850e4e54
spec:
imagePullSecrets:
[]
initContainers:
[]
containers:
- name: tasklist
image: camunda/tasklist:8.3.1
imagePullPolicy: IfNotPresent
securityContext:
allowPrivilegeEscalation: false
privileged: false
readOnlyRootFilesystem: true
runAsUser: 1002
env:
- name: SPRING_PROFILES_ACTIVE
value: "identity-auth"
- name: SPRING_SECURITY_OAUTH2_RESOURCESERVER_JWT_ISSUERURI
value: "https://some_url.com"
- name: SPRING_SECURITY_OAUTH2_RESOURCESERVER_JWT_JWKSETURI
value: "https://some_url.com"
- name: CAMUNDA_TASKLIST_IDENTITY_BASEURL
value: "http://camunda-devops-test-identity:8080"
- name: CAMUNDA_TASKLIST_IDENTITY_ISSUER_URL
value: "https://some_url.com"
- name: CAMUNDA_TASKLIST_IDENTITY_ISSUER_BACKEND_URL
value: "https://some_url.com"
- name: CAMUNDA_TASKLIST_IDENTITY_CLIENT_ID
value: "tasklist"
- name: CAMUNDA_TASKLIST_IDENTITY_CLIENT_SECRET
valueFrom:
secretKeyRef:
name: "camunda-devops-test-tasklist-identity-secret"
key: tasklist-secret
- name: CAMUNDA_TASKLIST_IDENTITY_AUDIENCE
value: "tasklist-api"
- name: CAMUNDA_TASKLIST_IDENTITY_REDIRECT_ROOT_URL
value: "https://some_url.com"
- name: ZEEBE_CLIENT_ID
value: zeebe
- name: ZEEBE_CLIENT_SECRET
valueFrom:
secretKeyRef:
name: "camunda-devops-test-zeebe-identity-secret"
key: zeebe-secret
- name: ZEEBE_AUTHORIZATION_SERVER_URL
value: "https://some_url.com"
- name: ZEEBE_TOKEN_AUDIENCE
value: zeebe-api
- name: GRAPHQL_PLAYGROUND_ENABLED
value: "true"
- name: GRAPHQL_PLAYGROUND_SETTINGS_REQUEST_CREDENTIALS
value: "include"
- name: HOME
value: /parent
- name: ZEEBE_CLIENT_CONFIG_PATH
value: /tmp/zeebe_auth_cache
resources:
limits:
cpu: 1000m
memory: 2Gi
requests:
cpu: 400m
memory: 1Gi
ports:
- containerPort: 8080
name: http
protocol: TCP
readinessProbe:
httpGet:
path: /actuator/health/readiness
scheme: HTTP
port: http
initialDelaySeconds: 30
periodSeconds: 30
successThreshold: 1
failureThreshold: 5
timeoutSeconds: 1
volumeMounts:
- name: config
mountPath: /app/resources/application.yml
subPath: application.yml
- mountPath: /tmp
name: tmp
- mountPath: /camunda
name: camunda
volumes:
- name: config
configMap:
name: camunda-devops-test-tasklist
defaultMode: 484
- name: tmp
emptyDir: {}
- name: camunda
emptyDir: {}
securityContext:
fsGroup: 1002
runAsNonRoot: true resources:
limits:
cpu: 1000m
memory: 2Gi
requests:
cpu: 400m
memory: 1Gi
PG2000
commented
1 year ago We're facing the same issues
aabouzaid
Describe the issue:
When Installing C8 with the 8.3.1 Helm Release, I face the following warnings:
I can see that some of the warnings are coming from the postgres bitnami chart (https://github.com/bitnami/charts/issues/17465).
For
W1026 10:50:43.612402 28001 warnings.go:70] unknown field "spec.template.spec.containers[0].limits" W1026 10:50:43.612483 28001 warnings.go:70] unknown field "spec.template.spec.containers[0].requests"
I am unsure where they are coming from
Actual behavior:
Installation throws warnings but deployment is still successful
Expected behavior:
No warnings are thrown, unless something needs to be fixed.
How to reproduce:
helm install camunda camunda/camunda-platformLogs:
Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.