Skip to content

add support for secret object, and allow adding CRD validation field#723

Open
mkl262 wants to merge 2 commits into
aws-controllers-k8s:mainfrom
mkl262:main
Open

add support for secret object, and allow adding CRD validation field#723
mkl262 wants to merge 2 commits into
aws-controllers-k8s:mainfrom
mkl262:main

Conversation

@mkl262

@mkl262 mkl262 commented Jul 16, 2026

Copy link
Copy Markdown

Issue #, if available:
required for aws-controllers-k8s/acm-controller#104

Description of changes:

  • Allow generated APIs to reference Secrets whose data keys are controlled by the controller.
  • support creation of x-kubernetes-validations fields in crd definitions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ack-prow
ack-prow Bot requested review from a-hilaly and knottnt July 16, 2026 19:52
@ack-prow

ack-prow Bot commented Jul 16, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mkl262
Once this PR has been reviewed and has the lgtm label, please assign a-hilaly for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@ack-prow ack-prow Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 16, 2026
@ack-prow

ack-prow Bot commented Jul 16, 2026

Copy link
Copy Markdown

Hi @mkl262. Thanks for your PR.

I'm waiting for a aws-controllers-k8s member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

mkl262 added 2 commits July 22, 2026 19:02
Allow generated APIs to reference Secrets whose data keys are controlled by the controller.
support creation of x-kubernetes-validations fields in crd definitions
Comment thread pkg/config/field.go
Comment on lines +425 to +428
// IsSecretReference instructs the code generator that this field should be
// a name/namespace-only SecretReference. Use this when the controller owns
// the Secret data key convention instead of accepting a user-selected key.
IsSecretReference bool `json:"is_secret_reference"`

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

i'm not sure if the difference between Secret and SecretReference is clear just from the names.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

maybe it can be something like isTLSSecret?

@mkl262 mkl262 Jul 23, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I thought of it as a generlized catch all for secrets that have a predefined structure, such as docker config, TLS, or ssh type secrets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants