Skip to content

Conversation

nlamirault
Copy link

@nlamirault nlamirault commented Aug 8, 2025

  • Support all Kubernetes recommended labels
  • Refactoring using template helper.
  • Support for additional labels which can be add to all resources
  • Change labelSelector into metrics-service to use the same of the deployment.

Signed-off-by: Nicolas Lamirault <[email protected]>
@ack-prow ack-prow bot requested review from knottnt and michaelhtm August 8, 2025 17:04
Copy link

ack-prow bot commented Aug 8, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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 Aug 8, 2025
Copy link

ack-prow bot commented Aug 8, 2025

Hi @nlamirault. 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.

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/test-infra repository.

@knottnt
Copy link
Contributor

knottnt commented Aug 19, 2025

Hi @nlamirault appreciate the contribution! In order to keep the common elements for the controller helm charts synced we use common templates in the code-generator repo. These changes should probably be done there.

@nlamirault
Copy link
Author

@knottnt how can i test the generation of the template using the code-generator ?

@knottnt
Copy link
Contributor

knottnt commented Aug 20, 2025

how can i test the generation of the template using the code-generator ?

@nlamirault Once you've updated the template files you could test locally by re-building the Helm charts of one of the ACK controller. For example from the code-generator repo the s3-controller could be rebuilt with make build-controller SERVICE=s3. You can find more info in our contributor docs.

@nlamirault
Copy link
Author

I try this one: aws-controllers-k8s/code-generator#619

@nlamirault
Copy link
Author

i've got this error. Any idea ?

$ export SERVICE=s3
$ make build-controller SERVICE=$SERVICE
building ack-generate ... ok.
==== building s3-controller ====
Error evaluating SERVICE_CONTROLLER_SOURCE_PATH environment variable:
/Users/nicolas.lamirault/Projects/Forks/ack-code-generator/scripts/../../s3-controller is not a directory.

Usage:
  build-controller.sh <service>

<service> should be an AWS service API aliases that you wish to build -- e.g.
's3' 'sns' or 'sqs'

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