Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pick Target Application by Selector instead of Label #4004

Open
arodindev opened this issue Jun 9, 2023 · 2 comments
Open

Pick Target Application by Selector instead of Label #4004

arodindev opened this issue Jun 9, 2023 · 2 comments

Comments

@arodindev
Copy link

Question

Hello, suppose i have the following two deployment definitions - note that they both have the same label.

my-app.yaml:

kind: Deployment
apiVersion: apps/v1
metadata:
  name: my-app
  namespace: default
  labels:
    app: my-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-app

my-app-primary.yaml:

kind: Deployment
apiVersion: apps/v1
metadata:
  name: my-app-primary
  namespace: default
  labels:
    app: my-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-app-primary

Now I would like to be able to select the deployment with selector my-app-primary. However, the dashboard does not provide an option to specify the selector. I can only select deployment by its label, but as you can see the label are identcial in both deployments. Is this possible with Litmus?

@neelanjan00
Copy link
Member

How about adding a unique label to the specific deployment you want to target?

@smitthakkar96
Copy link
Contributor

I think there are other use cases where one could really benefit from having support label selector instead of single label. One use-case that comes to my mind is automated fault injection to canary pods on rollout. The canary pods might have same app label but different label to identify if it's primary or canary or blue/green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants