Allow drivers to access devices on the host #332
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
Some drivers need direct access to host devices.
It is getting very irritating trying to work out which pod is which when they are all named with UUIDs. We are also running into k8s name length limits when k8s extends the Deployment name to create ReplicaSet and Pod names. Our `name` must be unique in any case, or everything breaks. Use a sanitised form of the name in our k8s resource names.
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.
Some device drivers necessarily need to access devices on the host. Allow the edge agent chart to map host devices into the driver containers.
Rework the edge agent k8s resource naming to use the node name instead of the UUID. The UUIDs are just getting annoying.