IT AI Index

Index › Vendors › Kubernetes YAML · September 2026 Edition

1 category · Named, not ranked

Kubernetes YAML

4Judge labels

0First choices

0Negative labels

2 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

2 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. Kubernetes YAML was named 2 times in IaC, where Terraform led with 46%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small businessnot named

No model named it for this buyer.

Mid-market27 of 46

under the label threshold

Enterprise23 of 64

under the label threshold

In iac · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Kubernetes YAML for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Infrastructure as code	Cloud and infrastructure	0%	27 of 46	0%	2	under 10 labels · led by Terraform at 46%

Movement

This is the first edition on this tier, so no move can be computed for Kubernetes YAML yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Kubernetes YAML across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Mention	Labels
Claude Haiku 4.5	1	1
GPT-5.4 mini	0	0
Gemini 3.5 Flash	0	0
Perplexity Sonar	0	0
Grok 4.1 Fast	0	0
Mistral Small	0	0
DeepSeek V4 Flash	0	0
Llama 4 Maverick	1	1
Qwen 3.7 Flash	0	0
Kimi K2	0	0
GLM 4.7 FlashX	0	0
MiniMax M2.5	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct0 labelsNone

Paraphrase0 labelsNone

Comparative2 labelsNone

Budget-constrained0 labelsNone

Scale-constrained0 labelsNone

Negative2 labelsNone

First choiceAlternativeMentionNegative4 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

No positive label carried a quote.

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as Kubernetes YAML, over the 4 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Kubernetes YAML was named but was not.

ProductSame answerTook the first choice insteadHead to head

Pulumi4 of 42Not in the top three

Terraform4 of 42Not in the top three

AWS CDK4 of 40Not in the top three

AWS CloudFormation4 of 40Not in the top three

Azure Bicep4 of 40Not in the top three

Azure Resource Manager templates4 of 40Not in the top three

Crossplane4 of 40Not in the top three

Google Cloud Infrastructure Manager4 of 40Not in the top three

OpenTofu3 of 41Not in the top three

Ansible3 of 40Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Kubernetes YAML. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 4 of the 4 answers that named Kubernetes YAML and are not a share of its labels.

Domains cited

pulumi.com4

guideflow.com3

spacelift.io3

bluelight.co2

cloudester.com2

firefly.ai2

sentinelone.com2

thectoclub.com2

blog.supportlobby.com1

carmatec.com1

Twenty-two of the twenty-two domain citations in answers naming Kubernetes YAML came from somebody else's page.

Pages cited

pulumi.com/blog/infrastructure-as-code-tools4

guideflow.com/blog/infrastructure-as-code-tools3

spacelift.io/blog/infrastructure-as-code-tools3

bluelight.co/blog/best-infrastructure-as-code-tools2

cloudester.com/infrastructure-as-code-tools2

sentinelone.com/cybersecurity-101/cloud-security/infrastructure-as-code-platforms2

thectoclub.com/tools/best-infrastructure-as-code-tools2

blog.supportlobby.com/terraform-vs-cloudformation-vs-ansible1

Pages are listed as the models cited them.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Kubernetes YAML's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Kubernetes YAML, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at kubernetes.io is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.