Open
Conversation
… apiURL to reconcilers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
A brief description of the change being made with this pull request.
Refactor secret refreshes to remove client recreation (which doesn't need to happen). Also removed callback system since all that needs to be remade is the
auth. Auth is now remade on every reconcile and passed down as a parameter, instead of a state.NOTE: Currently
apiURLis kept as a field inside the reconcilers. This might require a change oncecreds.gohas been refactored.Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Minimum Agent Versions
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
Describe your test plan
Write there any instructions and details you may have to test your PR.
Add volumeMount to
manager.yamland volume to pod spec
You should have your kind cluster created already. Create a configmap from your
secret_backendscript.kubectl create configmap secret-backend-script --from-file=secret_backend.shEnable all custom resources (or whichever custom resource you want to test client recreation with).
Add API/APP key in env vars. Make sure it is encrypted:
make deploywith this configuration inmanager.yaml(feel free to change refreshInterval; it's short for testing purposes).if the operator fails to find the configMap, run 4. again and delete the pod.
Checklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel