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

Add "error" option to resource level BotKube config #96

Closed
PrasadG193 opened this issue May 19, 2019 · 0 comments · Fixed by #98
Closed

Add "error" option to resource level BotKube config #96

PrasadG193 opened this issue May 19, 2019 · 0 comments · Fixed by #98
Assignees
Labels
enhancement New feature or request

Comments

@PrasadG193
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
As of now, if someone is interested in getting only error/failure events for particular resources, he/she has to add following configuration in BotKube:

  ## Resources you want to watch
  resources:
    - name: NAME_OF_THE_RESOURCE  
      namespaces: 
        - all

  # K8S error/warning events you want to receive for the configured resources
  events:
    types:
      - warning

This is quite difficult to read and understand. There should be an easier way to configure this.

Describe the solution you'd like
Instead of having events as a separate field in the BotKube configuration, we should have error as a additional field at resource level configuration

  ## Resources you want to watch
  resources:
    - name: NAME_OF_THE_RESOURCE  
      namespaces: 
        - all
      events:
        - create
        - update
        - delete
        - error
@PrasadG193 PrasadG193 added the enhancement New feature or request label May 19, 2019
@PrasadG193 PrasadG193 changed the title Add error option to resource level BotKube config Add "error" option to resource level BotKube config May 19, 2019
@PrasadG193 PrasadG193 self-assigned this May 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant