feat: align the argument types for k8s context

[kemingy]

Fixes N/A

Description

Update the argument types doc according to pkg/k8s/apis/cilium.io/v1alpha1/types.go

Changelog

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	4ad4362
🔍 Latest deploy log	https://app.netlify.com/projects/tetragon/deploys/6902df3b14dd340008ef050f
😎 Deploy Preview	https://deploy-preview-4213--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mtardy]

Thanks! Ah indeed some of the types are not reflected into the TracingPolicy API, @olsajiri since you created that page, I imagine you based yourself on

tetragon/pkg/generictypes/generictypes.go

Lines 81 to 132 in 27c9abe

	var genericStringToType = map[string]int{
	"string": GenericStringType,
	"int": GenericIntType,
	"uint64": GenericU64Type,
	"unsigned long": GenericU64Type,
	"ulong": GenericU64Type,
	"uint32": GenericU32Type,
	"sint64": GenericS64Type,
	"int64": GenericS64Type,
	"long": GenericS64Type,
	"sint32": GenericS32Type,
	"int32": GenericS32Type,
	"skb": GenericSkbType,
	"sock": GenericSockType,
	"size_t": GenericSizeType,
	"char_buf": GenericCharBuffer,
	"char_iovec": GenericCharIovec,
	"filename": GenericFilenameType,
	"file": GenericFileType,
	"path": GenericPathType,
	"fd": GenericFdType,
	"cred": GenericCredType,
	"const_buf": GenericConstBuffer,
	"nop": GenericNopType,
	"bpf_attr": GenericBpfAttr,
	"perf_event": GenericPerfEvent,
	"bpf_map": GenericBpfMap,
	"user_namespace": GenericUserNamespace,
	"capability": GenericCapability,
	"kiocb": GenericKiocb,
	"iov_iter": GenericIovIter,
	"load_info": GenericLoadModule,
	"module": GenericKernelModule,
	"syscall64": GenericSyscall64,
	"sint16": GenericS16Type,
	"int16": GenericS16Type,
	"uint16": GenericU16Type,
	"sint8": GenericS8Type,
	"int8": GenericS8Type,
	"uint8": GenericU8Type,
	"kernel_cap_t": GenericKernelCap,
	"cap_inheritable": GenericCapInheritable,
	"cap_permitted": GenericCapPermitted,
	"cap_effective": GenericCapEffective,
	"linux_binprm": GenericLinuxBinprmType,
	"data_loc": GenericDataLoc,
	"net_device": GenericNetDev,
	"sockaddr": GenericSockaddrType,
	"socket": GenericSocketType,
	"dentry": GenericDentryType,
	"bpf_prog": GenericBpfProgType,
	}

Do you know why we have this difference?

[mtardy]

So apparently instead of just deleting it from the docs we should either:

• document that these types are only supported in non-k8s context
• add support for k8s context, I don't think it should be too hard, it's just some plumbing missing

[kemingy]

So apparently instead of just deleting it from the docs we should either:

* document that these types are only supported in non-k8s context

* add support for k8s context, I don't think it should be too hard, it's just some plumbing missing

Will try to support those types for k8s context.

Actually, I'm not sure what the non-k8s context means. I run it with the local Docker container, but clearly it requires the tracepoints policy YAML file, and those types are rejected since they violate the protobuf.

[mtardy]

Will try to support those types for k8s context.

Cool! I think it's the better option here.

Actually, I'm not sure what the non-k8s context means. I run it with the local Docker container, but clearly it requires the tracepoints policy YAML file, and those types are rejected since they violate the protobuf.

Yeah previously they weren't validated because of a bug but indeed now they should be validated against the CRD so it should be rejected anyway.