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 vSphere metrics to report vCenter version #94651

Closed
Danil-Grigorev opened this issue Sep 9, 2020 · 3 comments · Fixed by #94526 or openshift/kubernetes#447
Closed

Add vSphere metrics to report vCenter version #94651

Danil-Grigorev opened this issue Sep 9, 2020 · 3 comments · Fixed by #94526 or openshift/kubernetes#447
Labels
area/provider/vmware Issues or PRs related to vmware provider kind/feature Categorizes issue or PR as related to a new feature. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.

Comments

@Danil-Grigorev
Copy link
Member

Danil-Grigorev commented Sep 9, 2020

What would you like to be added:

We need reporting of vSphere vCenter version to be shown in the metrics.

Why is this needed:

The goal behind this is to add some info about the underlying infrastructure for the kubernetes cluster. Some customers were experiencing issues during the cluster upgrades, but nothing in the upgrades themselves or kubernetes code for vSphere provider seemingly could cause those. The issue is storage related, and happening on a variety of releases with a significant delay from any other underlying infrastructure change, to which the kubernetes cluster has no relation and a way to know about. So knowing used vCenter hostnames, and vSphere versions associated with it over time would be extremely beneficial for debugging in similar circumstances.

Some of the use cases we face:

  1. A vSpehre DRS is enabled in a customer environment, and so there occurs a periodic automated vMotion for VMs backing kuberentes Nodes. We'd like to know on which host the actual kubernetes Node was located at any moment, and if any vCenter version transitions happened over time, new hosts added/removed/renamed.
@Danil-Grigorev Danil-Grigorev added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 9, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 9, 2020
@Danil-Grigorev
Copy link
Member Author

/sig cloud-provider
/wg provider-vsphere

@k8s-ci-robot k8s-ci-robot added the sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. label Sep 9, 2020
@k8s-ci-robot
Copy link
Contributor

@Danil-Grigorev: The label(s) wg/provider-vsphere cannot be applied, because the repository doesn't have them

In response to this:

/sig cloud-provider
/wg provider-vsphere

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 9, 2020
@Danil-Grigorev
Copy link
Member Author

/area provider/vmware

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/vmware Issues or PRs related to vmware provider kind/feature Categorizes issue or PR as related to a new feature. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.
Projects
None yet
2 participants