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
Description of the problem/feature request
Currently, we are starting to migrate our applications from Kubernetes Deployments to Argo Rollouts, which provides advanced deployment strategies, like bluegreen or canary. As stated in the Argo Rollouts docs:
A Rollout is Kubernetes workload resource which is equivalent to a Kubernetes Deployment object.
It is intended to replace a Deployment object in scenarios when more advanced deployment or progressive
delivery functionality is needed
Description of the existing behavior vs. expected behavior
When deleting our deployment, the dangling-service check included in kube-linter starts failing, because it can't match any pods, because in this case, the pods are now controlled by Argo Rollouts.
kube-linter lint app.yml
KubeLinter 0.6.8
/Users/romanmartin/DeveloperCorner/my-app/deploy/my-app/app.yml: (object: default/my-app /v1, Kind=Service) no pods found matching service labels (map[run:my-app]) (check: dangling-service, remediation: Confirm that your service's selector correctly matches the labels on one of your deployments.)
Error: found 1 lint errors
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Description of the problem/feature request
Currently, we are starting to migrate our applications from Kubernetes
Deployments
to ArgoRollouts
, which provides advanced deployment strategies, like bluegreen or canary. As stated in the Argo Rollouts docs:Description of the existing behavior vs. expected behavior
When deleting our deployment, the
dangling-service
check included in kube-linter starts failing, because it can't match any pods, because in this case, the pods are now controlled by Argo Rollouts.Input file:
kube-linter execution:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: