Skip to content

Conversation

@rishi-jat
Copy link
Contributor

Summary

Completes typed client support by adding generated shared informers, typed listers,
and reproducible code-generation tooling for tenancy APIs.

Follows standard Kubernetes client-go conventions.

Fixes #277

@kubestellar-prow kubestellar-prow bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Dec 25, 2025
@github-actions
Copy link

Thank you for submitting your first Pull Request to KubeStellar. We are delighted to have you in our Universe!

@kubestellar-prow kubestellar-prow bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Dec 25, 2025
@rishi-jat
Copy link
Contributor Author

/cc @MikeSpreitzer

@MikeSpreitzer
Copy link
Contributor

This PR needs evidence that it works as intended.
The functionality in this PR should be tested in CI.

@katara-Jayprakash
Copy link
Contributor

@rishi-jat hope you are doing well, could you fix these review points ?

@rishi-jat
Copy link
Contributor Author

Will do this as soon as possible. I’m currently out of town on holiday until 7 January and will address all the suggestions after that. Thanks!

Generated using k8s.io/code-generator v0.32.10:
- client-gen for typed clientset
- lister-gen for listers
- informer-gen for informers

API group: tenancy.kflex.kubestellar.org/v1alpha1
CRDs: ControlPlane, PostCreateHook (cluster-scoped)

Signed-off-by: Rishi Jat <[email protected]>
- New script compares freshly generated code against committed code
- Makefile verify-codegen target now uses verify-codegen.sh
- Removed dependency on update-codegen.sh (which requires clean tree)

Signed-off-by: Rishi Jat <[email protected]>
…dback and fix remaining comment

Signed-off-by: Rishi Jat <[email protected]>
Copy link
Contributor

@MikeSpreitzer MikeSpreitzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple minor comments left, could be fixed in this PR or a later one.
/lgtm
Thanks!

@kubestellar-prow kubestellar-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2026
@kubestellar-prow
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: 588be97d0b30c0701a4bbb138d663b2cbc0f8146

@kubestellar-prow kubestellar-prow bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2026

// Package v1alpha1 contains API Schema definitions for the tenancy v1alpha1 API group
// +kubebuilder:object:generate=true
// +k8s:deepcopy-gen=package
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"fixed" means that the removal was undone, right? Why was the removal undone?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the confusion. Here's what happened:

  1. First commit: I removed both +k8s:deepcopy-gen=package AND +kubebuilder:object:generate=true
  2. This caused the CI build to fail with errors like "DeepCopyInto undefined"
  3. Second commit: I restored only +kubebuilder:object:generate=true because it's needed for controller-gen to generate deepcopy methods

Current state of doc.go:

// +kubebuilder:object:generate=true
// +groupName=tenancy.kflex.kubestellar.org

The +k8s:deepcopy-gen=package marker is removed as you requested. The +kubebuilder:object:generate=true marker remains because without it, controller-gen doesn't generate the DeepCopyInto() methods that the code depends on.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Should I follow the kubestellar pattern exactly and remove the kubebuilder marker too? If so, how does kubestellar generate its deepcopy methods?

@rishi-jat
Copy link
Contributor Author

/retest

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes in this file are beyond the scope of this PR and are not mentioned in the PR's opening comment.

Copy link
Contributor

@MikeSpreitzer MikeSpreitzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good enough to merge, although there are still some open comments.
/lgtm
/approve

@kubestellar-prow kubestellar-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2026
@kubestellar-prow
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: a53443e192d45e7c0650cdd7f7fd1673fadcae38

@kubestellar-prow
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MikeSpreitzer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2026
@kubestellar-prow kubestellar-prow bot merged commit 3d600f3 into kubestellar:main Jan 9, 2026
9 checks passed
@clubanderson
Copy link
Contributor

/retest

clubanderson added a commit that referenced this pull request Jan 15, 2026
chore: remove stale workflow in favor of Prow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature: Add typed clients

5 participants