-
Notifications
You must be signed in to change notification settings - Fork 495
Controller gen #5543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Controller gen #5543
Conversation
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @zbb88888, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
I've introduced changes primarily focused on improving the generation of Custom Resource Definitions (CRDs) for Kube-OVN. This involves adding a new script to automate CRD generation using controller-gen and making necessary adjustments to Go struct tags to ensure proper JSON serialization for the generated CRDs.
Highlights
- CRD Generation Script: I've added a new shell script,
hack/update-codegen-crd.sh, which automates the process of generating CRDs usingcontroller-gen. This script ensures that the latest CRDs are always up-to-date with the Go API definitions. - Gitignore Update: I've updated the
.gitignorefile to includeyamls/crds, preventing generated CRD files from being committed to the repository directly, as they will now be generated on demand. - API Struct Tagging: I've added
jsontags to embedded structs withinProviderNetworkCondition,NatOutgoingPolicyRuleStatus, andBigInttypes. This ensures thatcontroller-gencorrectly processes these fields when generating CRDs, improving their serialization and deserialization.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a script to generate CRDs using controller-gen and updates several type definitions with JSON tags to support this. The changes are generally good, but I have a few suggestions to improve the new script's robustness and flexibility. I've also identified a potential issue with the JSON tag on the BigInt type which could lead to an incorrect CRD schema, and I've proposed a fix.
pkg/internal/big_int.go
Outdated
|
|
||
| type BigInt struct { | ||
| big.Int | ||
| big.Int `json:"bigInt"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a json tag to the embedded big.Int field might cause issues with CRD generation. The BigInt type has custom MarshalJSON and UnmarshalJSON methods that serialize it to a JSON string. However, controller-gen might interpret this json:"bigInt" tag to mean that the serialized form is an object with a bigInt field, leading to an incorrect OpenAPI schema for the CRD. This will cause schema validation failures for clients.
The recommended way to handle types with custom JSON marshalling is to use // +kubebuilder:validation:Type=string on the fields of type BigInt within your CRD structs (e.g., in IPPoolStatus). This tells controller-gen to treat it as a string in the schema, which matches the behavior of your custom marshaller.
Please remove this tag and apply the +kubebuilder marker on the relevant fields in the CRD definitions.
| big.Int `json:"bigInt"` | |
| big.Int |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
root@debian:~/f/kube-ovn controller-gen ✔ 3m ⍉
▶ bash ./hack/update-codegen-crd.sh
- export GOPROXY=https://goproxy.cn
- GOPROXY=https://goproxy.cn
- CONTROLLER_TOOLS_VERSION=v0.17.3
- go install sigs.k8s.io/controller-tools/cmd/[email protected]
- go mod tidy
- controller-gen crd:allowDangerousTypes=true paths=./pkg/apis/kubeovn/v1 output:crd:artifacts:config=./yamls/crds
/root/f/kube-ovn/pkg/internal/big_int.go:9:2: encountered struct field "" without JSON tag in type "BigInt"
github.com/kubeovn/kube-ovn/pkg/apis/kubeovn/v1:-: conflicting types in allOf branches in schema: object vs string
github.com/kubeovn/kube-ovn/pkg/apis/kubeovn/v1:-: conflicting types in allOf branches in schema: object vs string
github.com/kubeovn/kube-ovn/pkg/apis/kubeovn/v1:-: conflicting types in allOf branches in schema: object vs string
github.com/kubeovn/kube-ovn/pkg/apis/kubeovn/v1:-: conflicting types in allOf branches in schema: object vs string
Error: not all generators ran successfully
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: zbb88888 <[email protected]>
Pull Request Test Coverage Report for Build 19527788804Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
|
PRs go stale after 60d of inactivity. Please comment or re-open the PR if you are still working on this PR. |
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
问题根源:
controller-gen 分支引入 BigInt 类型替换 int64 用于 IP 地址计数,
但 MarshalJSON 实现返回裸数字而非带引号的字符串,与 CRD schema
(+kubebuilder:validation:Type=string) 不匹配,导致 K8s API server
在 patch/create 操作时拒绝请求。
修复内容:
1. BigInt.MarshalJSON: 输出带引号的 JSON 字符串 ("123" 而非 123)
2. BigInt.UnmarshalJSON: 兼容处理带引号和裸数字格式(向后兼容)
3. BigInt.DeepCopyInto: 修复错误实现 (FillBytes -> Int.Set)
测试覆盖:
- pkg/types/big_int_test.go: 完整的 BigInt 单元测试
* JSON 序列化/反序列化(包含边界情况)
* 算术运算 (Add/Sub)
* 比较操作 (Cmp/Equal/EqualInt64)
* DeepCopy 语义正确性
* 结构体嵌入场景
- pkg/apis/kubeovn/v1/subnet_bigint_test.go: SubnetStatus 集成测试
* 验证 Subnet CRD 对象的 JSON 序列化符合 K8s API 规范
* 模拟 patch 操作确保字段类型正确(string 而非 number)
影响范围:
修复 E2E 测试失败:
[group:subnet] should support subnet add nat outgoing policy rules
所有 BigInt 类型字段现在正确序列化为符合 CRD schema 的 JSON 字符串,
确保与 K8s API server 的兼容性。
Signed-off-by: zbb88888 <[email protected]>
验证 BigInt 类型在真实 Kubernetes API Server 交互中的正确性: 测试覆盖: 1. 创建 Subnet 后 BigInt 字段正确填充 2. JSON 序列化格式验证(字符串而非数字) 3. K8s API patch 操作成功(验证不会因类型不匹配被拒绝) 4. 状态字段直接更新(关键:通过 API 更新 BigInt 字段) 5. 大数值往返序列化(/16 subnet = 65533 IPs) 关键验证点: - 确保 BigInt.MarshalJSON 返回 "253" 而非 253 - 确保符合 CRD schema type:string 要求 - 防止 API server 因类型校验失败拒绝 patch 补充单元测试未覆盖的 K8s API 层面交互。 Signed-off-by: zbb88888 <[email protected]>
修复 golangci-lint 错误: test/e2e/kube-ovn/subnet/subnet_bigint_e2e_test.go:123:3: declared and not used: currentSubnet (typecheck) 变量 currentSubnet 仅用于验证 subnet 存在,实际不需要使用其返回值。 直接移除该变量声明,测试逻辑不受影响。 Signed-off-by: zbb88888 <[email protected]>
修复4个 lint 问题: 1. goimports: 调整 import 顺序,将标准库、k8s 包和本地包分组 pkg/apis/kubeovn/v1/subnet_bigint_test.go 2. gofumpt: 函数参数格式化 checkStringField := func(name, expected string) 3. revive: 移除 min 函数定义,使用 Go 1.21+ 内置 min 函数 (Go 1.21 及以上版本内置了 min/max 函数) 4. staticcheck QF1008: 简化 DeepCopyInto 选择器 n.Set(&b.Int) 替代 n.Int.Set(&b.Int) (嵌入字段可以直接访问方法) 所有单元测试通过验证。 Signed-off-by: zbb88888 <[email protected]>
- 修复 golangci-lint modernize 检查
- 在 subnet_bigint_test.go 中替换 3 处 interface{}
- 在 subnet_bigint_e2e_test.go 中替换 4 处 interface{}
- 保持测试逻辑不变
Signed-off-by: zbb88888 <[email protected]>
- 修复 golangci-lint modernize 检查
- 在 subnet_bigint_test.go 中替换 3 处 interface{}
- 在 subnet_bigint_e2e_test.go 中替换 4 处 interface{}
- 保持测试逻辑不变
Signed-off-by: zbb88888 <[email protected]>
Signed-off-by: zbb88888 <[email protected]>
Pull Request
What type of this PR
Examples of user facing changes:
Which issue(s) this PR fixes
Fixes #(issue-number)