validator-plugin-vsphere

The vSphere validator plugin ensures that your vSphere environment matches a user-configurable expected state.

Description

The vSphere validator plugin reconciles VsphereValidator custom resources to perform the following validations against your vSphere environment:

Compare a user's privileges with respect to a particular entity against an expected privilege set.

Supported entities:
- Cluster, Datacenter, Datastore, Folder, ESXi Host, Network, Resource Pool, vApp, vCenter root, Distributed Port Group, Distributed Switch
Required Privileges:
- System.View
Check if sufficient compute resources are available on a particular entity to satify a resource request.

Supported entities:
- Cluster, ESXi Host, Resource Pool
Required Privileges:
- TODO: identify and update
Compare the tags associated with a particular entity against an expected tag set.

Supported entities:
- Cluster, Datacenter, ESXi Host, Resource Pool, VM
Required Privileges:
- - TODO: identify and update
Check if a given set of ESXi Hosts all have NTP enabled and running, with identical NTP servers configured.

Required Privileges:
- - TODO: identify and update

Each VsphereValidator CR is (re)-processed every two minutes to continuously ensure that your vSphere environment matches the expected state.

See the samples directory for example VsphereValidator configurations.

Getting Started

You’ll need a Kubernetes cluster to run against. You can use KIND to get a local cluster for testing, or run against a remote cluster. Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).

Running on the cluster

Install Instances of Custom Resources:

kubectl apply -f config/samples/

Build and push your image to the location specified by IMG:

make docker-build docker-push IMG=<some-registry>/validator-plugin-vsphere:tag

Deploy the controller to the cluster with the image specified by IMG:

make deploy IMG=<some-registry>/validator-plugin-vsphere:tag

Uninstall CRDs

To delete the CRDs from the cluster:

make uninstall

Undeploy controller

UnDeploy the controller from the cluster:

make undeploy

Contributing

All contributions are welcome! Feel free to reach out on the Spectro Cloud community Slack.

Make sure pre-commit is installed.

Install the pre-commit scripts:

pre-commit install --hook-type commit-msg
pre-commit install --hook-type pre-commit

How it works

This project aims to follow the Kubernetes Operator pattern.

It uses Controllers, which provide a reconcile function responsible for synchronizing resources until the desired state is reached on the cluster.

Test It Out

Install the CRDs into the cluster:

make install

Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):

make run

NOTE: You can also run this in one step by running: make install run

Modifying the API definitions

If you are editing the API definitions, generate the manifests such as CRs or CRDs using:

make manifests

NOTE: Run make --help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.