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

Basic monitoring for the cluster #15

Open
mnkg561 opened this issue Mar 25, 2020 · 0 comments
Open

Basic monitoring for the cluster #15

mnkg561 opened this issue Mar 25, 2020 · 0 comments
Labels

Comments

@mnkg561
Copy link
Contributor

mnkg561 commented Mar 25, 2020

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST

What happened:
At the moment, cluster controller checks the connectivity every regular interval(configurable from config map) and validates the connectivity between manager and target cluster and updates the status.

This provides us the opportunity to add some more monitoring based on the configuration. For ex: If administrator wants to monitor specific set of pods in a target cluster in a known namespace.

May be something like:
Monitor:

  • name: kube-system-ns-monitor
    type: Pod
    min: 3
    maxAllowedFailureIntervals: 3
    result: warning/error
  • name: some-system-deploymennt-monitor
    type: Deployment
    name: manager-server
    maxAllowedFailureIntervals: 3
    result: warning/error
    What you expected to happen:
    Based on the monitoring, cluster state should change from Ready/Warning/Error

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
Still need to think about it and see whether its feasible and worth it
Environment:

  • manager version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

- controller logs:

$ kubectl logs

@mnkg561 mnkg561 added enhancement New feature or request cluster controller labels Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant