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
{{ message }}
This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
Describe the bug
When a module with a name greater than some specific threshold is deployed it gives some error related to the size of a labels.
To Reproduce
Steps to reproduce the behavior:
Install charlescd 1.0.0 or 1.0.1
Configure workspace and modules
Deploy a module named "notification-connector"
Check for replica error
Expected behavior
Expected the module to be deployed successfully
Screenshots
Your Environment
CharlesCD version used: 1.0.0 and 1.0.1
Description of environment where CharlesCD is running: GKE (1.20.12-gke.1500)
Browser Name and version (if applicable):
Additional context
Error:
type: ReplicaFailure
status: 'True'
lastTransitionTime: '2021-12-20T14:51:18Z'
reason: FailedCreate
message: >-
Pod "notification-connector-v73ecd7a-a2f58396-fd71-4d9c-9fdc-bcnqhzx" is
invalid: metadata.labels: Invalid value:
"notification-connector-v73ecd7a-a2f58396-fd71-4d9c-9fdc-bc16a014143f":
must be no more than 63 characters
Describe the bug
When a module with a name greater than some specific threshold is deployed it gives some error related to the size of a labels.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected the module to be deployed successfully
Screenshots
Your Environment
Additional context
Error:
status: 'True'
lastTransitionTime: '2021-12-20T14:51:18Z'
reason: FailedCreate
message: >-
Pod "notification-connector-v73ecd7a-a2f58396-fd71-4d9c-9fdc-bcnqhzx" is
invalid: metadata.labels: Invalid value:
"notification-connector-v73ecd7a-a2f58396-fd71-4d9c-9fdc-bc16a014143f":
must be no more than 63 characters
labels configured in the deployment.yaml
labels: component: {{ .Values.component }} tag: {{ .Values.tag }} circleId: {{ .Values.circleId }}
The text was updated successfully, but these errors were encountered: