Skip to content
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

feat: enables Kubernetes syncing for flagd #82

Merged
merged 7 commits into from
Sep 14, 2022
Merged

Conversation

AlexsJones
Copy link
Member

@AlexsJones AlexsJones commented Aug 31, 2022

  • This now will default to the Kubernetes sync provider
  • It will check and append the current SA to the cluster rolebinding for the flagD notifier API

@AlexsJones AlexsJones changed the title enables kuberentes syncing for flagd feat: enables kuberentes syncing for flagd Aug 31, 2022
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
@AlexsJones AlexsJones marked this pull request as ready for review September 6, 2022 14:58
@AlexsJones AlexsJones changed the title feat: enables kuberentes syncing for flagd feat: enables Kubernetes syncing for flagd Sep 6, 2022
@beeme1mr
Copy link
Member

Hey @AlexsJones, sorry this hasn't been reviewed yet. I've added @james-milligan and @skyerus to see if they can take a look tomorrow.

config/samples/end-to-end.yaml Outdated Show resolved Hide resolved
…e bindings

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Copy link
Member

@toddbaert toddbaert 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 a great change.

This now will default to the Kubernetes sync provider

I think this is totally justified now.

Is it worth mentioning this automatic role-binding in the readme?

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
@AlexsJones
Copy link
Member Author

This is a great change.

This now will default to the Kubernetes sync provider

I think this is totally justified now.

Is it worth mentioning this automatic role-binding in the readme?

I don't think it's necessary, it's part of the machinery. But happy welcome other opinions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants