Create an edge MQTT broker helm chart #379
Merged
Conversation
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
The original design was that an edge deployment was focussed on an Edge Agent, with sidecar charts deployed as needed. It has turned out to be better to deploy subsidiary charts as separate deployments because of the values handling; the objects defining these should not be in the _Call Gateway_ class. Create a class for them.
AlexGodbehere
approved these changes
Nov 27, 2024
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.
Create a new edge helm chart which deploys an MQTT broker. This broker is exposed to the cluster as service; the chart also provides the option to expose it on an external IP.
No security is currently implemented, beyond a default of
internalTrafficPolicy: Localwhich should prevent off-node pods from contacting the broker but is not intended as a security feature.