-
Notifications
You must be signed in to change notification settings - Fork 352
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
Add a "master" trait #1234
Milestone
Comments
relates to #259 |
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 14, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 14, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 14, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 14, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 14, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 15, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 16, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 16, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 16, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 16, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 16, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 16, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 20, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 20, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 20, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 20, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 20, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 20, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
that referenced
this issue
Feb 21, 2020
nicolaferraro
added a commit
that referenced
this issue
Feb 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can provide a trait for automatically configure the master component (or route policy?).
The trait should give the pod service account enough privileges to read/watch pods and read/write/watch configmaps, then configure some defaults.
It's likely that we don't need anything from runtime as the component can be automatically configured like here.
It's important that we always generate a new service account for the integration (no matter if we use master), unless the user specifies his own service account in spec.
Roles should be bound to the pod service account.
The text was updated successfully, but these errors were encountered: