This repository has been archived by the owner on Jun 23, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Configure flexvolume driver with secret #113
Merged
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
harveylowndes
force-pushed
the
configure-flexvolume-driver-with-secret
branch
2 times, most recently
from
May 10, 2018 09:49
85ebf05
to
1976ac4
Compare
harveylowndes
force-pushed
the
configure-flexvolume-driver-with-secret
branch
from
May 14, 2018 12:49
1976ac4
to
98879c7
Compare
harveylowndes
commented
May 14, 2018
@@ -16,13 +16,13 @@ installed on every node in your Kubernetes cluster. | |||
|
|||
### Kubernetes DaemonSet Installer | |||
|
|||
The recommended way to install the driver is through the daemonset installer mechanism. | |||
The recommended way to install the driver is through the daemonset installer mechanism. This will create two daemonsets, one specifically for master nodes, allowing configuration via a Kubernetes Secret, and one for worker nodes. |
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.
Check working here.
harveylowndes
commented
May 14, 2018
--from-file=config.yaml=config.yaml | ||
``` | ||
|
||
Once the Secret is set and the daemonsets deployed, the configuration file will be placed onto the master nodes. |
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.
Does the user need to know this?
@harveylowndes needs a rebase to resolve conflicts. |
owainlewis
approved these changes
Jun 1, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix: #109
Splits the daemon set into two: one for the master nodes and one for the worker nodes. The configuration file can be configured in a secret which is then placed on the master nodes.
kubectl create secret generic oci-flexvolume-driver \ -n kube-system \ --from-file=config.yaml=config.yaml