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
Describe the bug
We are using Terraform provider to deploy our charts. This allows us to provide some values at deployment time (usually infrastructure resources IDs etc.). Recently we've added alerts for pods resource consumption. To be DRY we've moved real values for resources to Terraform files from which they can be used for chart deployments and as alerts thresholds. To be able to template chart we still needed to have some values in resources so we've used "DEPLOY_TIME_VARIABLE" like we do for other deployment time values. After this change kube-linter is failing with error message: .../my-service/templates/service.yaml: (object: <no namespace>/my-service-api-svc /v1, Kind=Service) no pods found matching service labels (map[app:myservice]) (check: dangling-service, remediation: Confirm that your service's selector correctly matches the labels on one of your deployments.) which seems to be not valid as the only change that was done was to values of the resources.
Error messages which would clearly indicate root-cause of the issue.
It should be possible to configure linter to accept any value for resources including placeholders and only warn user if it cannot check if the value seems to be reasonable but it should not count it as error.
The text was updated successfully, but these errors were encountered:
test.yaml: (object: my_namespace_name/my_service_name /v1, Kind=Service) no pods found matching service labels (map[name:my_label_value]) (check: dangling-service, remediation: Confirm that your service's selector correctly matches the labels on one of your deployments.)
You can fix the warning by changing cpu: 10wrong_unit to cpu: 10m.
System info:
Describe the bug
We are using Terraform provider to deploy our charts. This allows us to provide some values at deployment time (usually infrastructure resources IDs etc.). Recently we've added alerts for pods resource consumption. To be DRY we've moved real values for
resources
to Terraform files from which they can be used for chart deployments and as alerts thresholds. To be able to template chart we still needed to have some values inresources
so we've used"DEPLOY_TIME_VARIABLE"
like we do for other deployment time values. After this change kube-linter is failing with error message:.../my-service/templates/service.yaml: (object: <no namespace>/my-service-api-svc /v1, Kind=Service) no pods found matching service labels (map[app:myservice]) (check: dangling-service, remediation: Confirm that your service's selector correctly matches the labels on one of your deployments.)
which seems to be not valid as the only change that was done was to values of theresources
.From:
to:
Sample YAML input
Expected behavior
resources
including placeholders and only warn user if it cannot check if the value seems to be reasonable but it should not count it as error.The text was updated successfully, but these errors were encountered: