feat(kubevirt): Add basic VM creation toolset

[lyarwood]

Summary

This PR introduces an initial KubeVirt toolset for the kubernetes-mcp-server, enabling AI agents to create virtual machines through MCP tools.

New Tools

vm_create

Provides VM creation with automatic resource resolution:

• Workload Matching: Auto-resolves OS names (fedora, ubuntu, rhel, etc.) to container disks or DataSources
• Resource Selection:
  • Auto-selects instancetypes based on size/performance hints
  • Auto-matches preferences based on workload names
  • Supports DataSource defaults
• Flexible Configuration: Supports both cluster-scoped and namespaced instancetypes/preferences
• Configurable Storage: Customizable root disk size (default: 30Gi)

Example Usage

Basic VM with auto-selected resources

  {
    "name": "vm_create",
    "arguments": {
      "namespace": "vms",
      "name": "my-vm",
      "workload": "fedora"
    }
  }

VM with specific size and performance hints

  {
    "name": "vm_create",
    "arguments": {
      "namespace": "vms",
      "name": "my-vm",
      "workload": "rhel",
      "size": "large",
      "performance": "compute-optimized",
      "storage": "100Gi"
    }
  }

VM with explicit instancetype and preference

  {
    "name": "vm_create",
    "arguments": {
      "namespace": "vms",
      "name": "my-vm",
      "workload": "ubuntu",
      "instancetype": "u1.medium",
      "preference": "ubuntu",
      "autostart": true
    }
  }

VM with custom container disk image

  {
    "name": "vm_create",
    "arguments": {
      "namespace": "vms",
      "name": "my-vm",
      "workload": "quay.io/myrepo/custom-os:v1.0",
      "size": "xlarge",
      "storage": "200Gi"
    }
  }

[Cali0707]

it would be nice if gevals included /cost and /context data allowing us to assert against it potentially.

@lyarwood +1 from my side on that being nice, the reason we haven't been able to add it there is that we use claude code in the non-interactive setup in gevals, and we haven't been able to figure out how to get that information in the non interactive setup. If you have any ideas, let me know and/or open a PR!

[codingben]

Good work Lee. Please consider creating a single VM package with tool.go that will have all VM's actions in one single place, it would help to avoid duplications and will be much better in terms of readablity and maintainability.

[codingben]

Thanks Lee.

Just an opinion: For the beginning I see too many folders and scripts to achieve a few VM's actions via MCP tooling. I'd ask the project's maintainers opinion about this, eventually this repository's codebase can be very huge.

[lyarwood]

Thanks Lee.

Just an opinion: For the beginning I see too many folders and scripts to achieve a few VM's actions via MCP tooling. I'd ask the project's maintainers opinion about this, eventually this repository's codebase can be very huge.

Assuming you are talking about the test directory, I agree it is indeed pretty large at the moment but I've already spoken to folks about improvements to the gevals framework that would help reduce that. I plan on working on introducing builtin agent support and configurable models for the openai-agent this week but until that is merged we will need to carry the extra scripts and config for now.

[manusa]

There's already a ToRESTConfig method to cover this functionality and implement the RESTClientGetter interface required for Helm:

kubernetes-mcp-server/pkg/kubernetes/manager.go

Lines 195 to 198 in 7f4edfd

	// ToRESTConfig returns the rest.Config object (genericclioptions.RESTClientGetter)
	func (m *Manager) ToRESTConfig() (*rest.Config, error) {
	return m.cfg, nil
	}

Similarly, there's already a ToDiscoveryClient method too (I think you're creating it at some point in the toolset).

Nonetheless, we need to prevent accessing any kubernetes API without checking if the resource is allowed by configuration:

kubernetes-mcp-server/pkg/kubernetes/accesscontrol.go

Lines 11 to 36 in cad863f

	// isAllowed checks the resource is in denied list or not.
	// If it is in denied list, this function returns false.
	func isAllowed(
	staticConfig *config.StaticConfig, // TODO: maybe just use the denied resource slice
	gvk *schema.GroupVersionKind,
	) bool {
	if staticConfig == nil {
	return true
	}
	for _, val := range staticConfig.DeniedResources {
	// If kind is empty, that means Group/Version pair is denied entirely
	if val.Kind == "" {
	if gvk.Group == val.Group && gvk.Version == val.Version {
	return false
	}
	}
	if gvk.Group == val.Group &&
	gvk.Version == val.Version &&
	gvk.Kind == val.Kind {
	return false
	}
	}
	return true
	}

In general, we don't want to directly expose the Kuberentes API to the toolsets implementors and provide whatetever is needed in the kubernetes package.

[lyarwood]

@manusa ACK apologies, pushed 9a977dc that should address this.

[Cali0707]

@lyarwood what is the use case where the ResourcesList doesn't work?

[lyarwood]

Ah apologies, should be fixed by 9cd97b4

[manusa]

LGTM, thx!

I added an additional commit to move the toolset tests to the MCP layer.
We are now testing the behavior from the MCP client up to the Kube API layer at no cost.

Production code looks good; there are a few optimizations that can be done, but I suppose we can defer these to follow up PRs.

[ksimon1]

/lgtm

[lyarwood]

/lgtm

[Cali0707]

LGTM, thanks for all the hard work on this @lyarwood @ksimon1 @manusa !