You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor!: remove RolePrivilegeValidationRules, add enums to API, remove "cloud" refs and simplify account handling (#357)
## Issue
N/A
## Description
- Remove RolePrivilegeValidationRules
- Document that the `System.View` privilege is required
- Make entityType an enum for proper validation
---------
Signed-off-by: Tyler Gillson <tyler.gillson@gmail.com>
- TODO: identify and update any additional required privileges
22
+
2. Check if sufficient compute resources are available on a particular entity to satify a resource request.
23
+
24
+
Supported entities:
25
+
- Cluster, ESXi Host, Resource Pool
26
+
27
+
Required Privileges:
28
+
- TODO: identify and update
29
+
3. Compare the tags associated with a particular entity against an expected tag set.
30
+
31
+
Supported entities:
32
+
- Cluster, Datacenter, ESXi Host, Resource Pool, VM
33
+
34
+
Required Privileges:
35
+
-- TODO: identify and update
36
+
4. Check if a given set of ESXi Hosts all have NTP enabled and running, with identical NTP servers configured.
37
+
38
+
Required Privileges:
39
+
-- TODO: identify and update
19
40
20
41
Each `VsphereValidator` CR is (re)-processed every two minutes to continuously ensure that your vSphere environment matches the expected state.
21
42
22
43
See the [samples](https://github.com/validator-labs/validator-plugin-vsphere/tree/main/config/samples) directory for example `VsphereValidator` configurations.
23
44
24
-
> [!NOTE]
25
-
> This plugin currently require a user with administrator role to perform all of the validations specified above. Further information on fine-grained permissions required by each validation will be updated in the future.
26
-
27
45
## Getting Started
28
46
You’ll need a Kubernetes cluster to run against. You can use [KIND](https://sigs.k8s.io/kind) to get a local cluster for testing, or run against a remote cluster.
29
47
**Note:** Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster `kubectl cluster-info` shows).
0 commit comments