-
Notifications
You must be signed in to change notification settings - Fork 727
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
Simplify setup of Enterprise Search access through Kibana UI #4598
Merged
Merged
Changes from 25 commits
Commits
Show all changes
29 commits
Select commit
Hold shift + click to select a range
caf46b8
Introduce Enterprise Search reference to the Kibana CRD
sebgl 243c146
Move ent naming functions around for better reuse
sebgl 0e2bdfe
Rely on convenient kibana.ESAssociation() accessor
sebgl e22a187
Add k8s.ObjectExists() help function
sebgl 4aa8b96
Homogenize association controllers labels comments
sebgl c9505e3
Make ES user creation optional in the assoc controller through an opt…
sebgl 23822ca
Add kibana-ent association controller
sebgl 86a183e
Check whether the referenced resource (not necessarily es) exists
sebgl 27d89af
Configure Kibana for Enterprise Search connectivity
sebgl e808dba
Allow association configuration with no es auth (secretName: "-")
sebgl 06e5556
Make the association controller reconciliation work when no es auth i…
sebgl f978a98
Unrelated typo fix
sebgl 01cedb8
Minor association controller unit test fixes
sebgl c794a4e
Make multi-association watches work when no ES reference is required
sebgl 2e007db
Add an integration test for Kibana<->Enterprise Search association st…
sebgl 06dd152
Add missing license header
sebgl 0641609
Make linter happier
sebgl 4dcebbd
Rename AssociatedNamer to ReferencedResourceNamer
sebgl 9a7a987
Refactor dynamic watches
sebgl 2863996
Remove the need for ReferencedResourceExists()
sebgl 084b668
Fix unit tests
sebgl 18836be
Fixes from PR review
sebgl 3da7275
Make linter happy
sebgl 20522ab
Fix comments
sebgl edac7aa
Report es association status in status.elasticsearchAssociationStatus
sebgl b5a11e3
Regen CRDs
sebgl e8585d4
Gen api docs
sebgl b64d912
Regen v1beta1 crds
sebgl c4ae1a0
Fix kibana status e2e test
sebgl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming here that no secret will ever be named "-". Since this is a value we set with our own secret naming scheme it should be OK.
It's somewhat nice because it doesn't break the existing schema and is quite easy to manipulate in the code.
However it also feels a bit "implicit", we could also modify the assoc conf schema to make things more explicit. WDYT?