Feat: add topology with cue rules for resources

[FogDong]

Get resource topology with rules like:

rules: [{
	group: "apps",
	resource: "Deployment",
	subResources: [{
		group: "apps",
		resource: "StatefulSet",
		selector: {
			ownerReference: true,
		},
	}],
	peerResources: [{
		group: "",
		resource: "ConfigMap",
		selector: {
			name: context.data.metadata.name,
		},
	}, {
		group: "",
		resource: "ConfigMap",
		selector: {
			namespace: "cm",
		},
	}, {
		group: "",
		resource: "ConfigMap",
		selector: {
			annotations: "anno": "value",
		},
	},  {
		group: "",
		resource: "ConfigMap",
		selector: {
			labels: "label": "value",
		},
	}, {
		group: "",
		resource: "Service",
		selector: {
			builtin: "service"
		}
	}],
}, {
	group: "apps",
	resource: "StatefulSet",
	subResources: [{
		group: "",
		resource: "Pod",
		selector: {
			ownerReference: true,
		},
	}],
}]

[Somefive]

Great!

[wangyikewxgm]

Could you provide an example of what the rules should look like to support the FluxCD Helm component?

[FogDong]

Could you provide an example of what the rules should look like to support the FluxCD Helm component?

If it is a FluxCD Helm component, then its rule should be like this:

rules: [{
	group: "fluxcd",
	resource: "HelmRelease",
	peerResources: [{
		group: "fluxcd",
		resource: "HelmRepo",
		selector: {
			name: context.data.metadata.name,
		},
	},
}]

But I'm not sure you want these two resources or the whole resources that created by a Helm Chart.

[codecov]

Codecov Report

Patch coverage: 93.09% and project coverage change: +0.38 🎉

Comparison is base (a2c10c3) 90.04% compared to head (ea246ed) 90.43%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
+ Coverage   90.04%   90.43%   +0.38%     
==========================================
  Files          62       64       +2     
  Lines        2110     2414     +304     
==========================================
+ Hits         1900     2183     +283     
- Misses        154      168      +14     
- Partials       56       63       +7     

Flag	Coverage Δ
unit-test	90.43% <93.09%> (+0.38%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
util/k8s/resource.go	75.67% <75.67%> (ø)
util/resourcetoplogy/topology.go	95.50% <95.50%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[wangyikewxgm]

Could you provide an example of what the rules should look like to support the FluxCD Helm component?

If it is a FluxCD Helm component, then its rule should be like this:

rules: [{
	group: "fluxcd",
	resource: "HelmRelease",
	peerResources: [{
		group: "fluxcd",
		resource: "HelmRepo",
		selector: {
			name: context.data.metadata.name,
		},
	},
}]

But I'm not sure you want these two resources or the whole resources that created by a Helm Chart.

I mean how to list resources deployed by fluxcd helmRelease, the resources has a special labels point to the helmRelease. Such as this deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
 annotations:
   deployment.kubernetes.io/revision: "1"
   meta.helm.sh/release-name: nginx-ingress
   meta.helm.sh/release-namespace: vela-system
 labels:
   helm.toolkit.fluxcd.io/name: nginx-ingress
   helm.toolkit.fluxcd.io/namespace: vela-system
 name: nginx-ingress-ingress-nginx-controller
 namespace: vela-system