Adjusted init fleet script to enable monitoring #229
Merged
Conversation
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
jeremiaswerner
approved these changes
Sep 5, 2025
Collaborator
jeremiaswerner
left a comment
jeremiaswerner
left a comment
There was a problem hiding this comment.
LGTM. Pls also update the screenshot in the README.md
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.
This PR enables Monitoring for fleet workers.
Furthermore, the script reworks the flow of the script and introduces poor-man idempotency (aka the script can be executed multiple-times to consume configuration updates)
Last, the script removes the registry secret
fleet-registry-secretwhich was backed by a Personal APIKey. Instead each project is being initialized with the corresponding IBM Code Engine managed registry location. E.g. for Frankfurt