-
Notifications
You must be signed in to change notification settings - Fork 746
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
28a4c12
commit 022d903
Showing
1 changed file
with
21 additions
and
58 deletions.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,81 +13,44 @@ | |
|
|
||
| kubectl create namespace argo-events | ||
|
|
||
| 2. Deploy Argo Events, SA, ClusterRoles, Sensor Controller, EventBus and EventSource Controller | ||
| 2. Deploy Argo Events, SA, ClusterRoles, Sensor Controller, EventBus Controller and EventSource Controller | ||
|
|
||
| kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/install.yaml | ||
|
|
||
| NOTE: | ||
|
|
||
| * On GKE, you may need to grant your account the ability to create new custom resource definitions and clusterroles | ||
|
|
||
| kubectl create clusterrolebinding YOURNAME-cluster-admin-binding --clusterrole=cluster-admin [email protected] | ||
| NOTE: | ||
| * On Openshift, make sure to grant `anyuid` scc to the service account. | ||
|
|
||
| #### Namespace Installation | ||
|
|
||
| 1. Create the namespace | ||
|
|
||
| kubectl create namespace argo-events | ||
| * On GKE, you may need to grant your account the ability to create new custom resource definitions and clusterroles | ||
|
|
||
| kubectl create clusterrolebinding YOURNAME-cluster-admin-binding --clusterrole=cluster-admin [email protected] | ||
| * On Openshift, make sure to grant `anyuid` scc to the service account. | ||
|
|
||
| 2. Deploy Argo Events, SA, Roles, Sensor Controller, EventBus and EventSource Controller | ||
| 3. Deploy the eventbus, | ||
|
|
||
| kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/namespace-install.yaml | ||
|
|
||
| NOTE: | ||
|
|
||
| * On GKE, you may need to grant your account the ability to create new custom resource definitions | ||
|
|
||
| kubectl create clusterrolebinding YOURNAME-cluster-admin-binding --clusterrole=cluster-admin [email protected] | ||
| * On Openshift, make sure to grant `anyuid` scc to the service account. | ||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/examples/eventbus/native.yaml | ||
|
|
||
| #### Step-by-Step Installation | ||
| #### Namespace Installation | ||
|
|
||
| 1. Create the namespace | ||
|
|
||
| kubectl create namespace argo-events | ||
|
|
||
| 2. Create the service account | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/argo-events-sa.yaml | ||
|
|
||
| 3. Create the role | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/namespace-install/rbac/argo-events-role.yaml | ||
| 2. Deploy Argo Events, SA, Roles, Sensor Controller, EventBus Controller and EventSource Controller | ||
|
|
||
| 4. Create the rolebinding | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/namespace-install/rbac/argo-events-role-binding.yaml | ||
|
|
||
| 5. Install the sensor custom resource definition | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/crds/argoproj.io_sensors.yaml | ||
|
|
||
| 6. Install the eventbus custom resource definition | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/crds/argoproj.io_eventbus.yaml | ||
|
|
||
| 7. Install the event-source custom resource definition | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/crds/argoproj.io_eventsources.yaml | ||
|
|
||
| 9. Deploy the sensor controller | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/sensor-controller/sensor-controller-deployment.yaml | ||
|
|
||
| 10. Deploy the eventbus controller | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/eventbus-controller/eventbus-controller-deployment.yaml | ||
| kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/namespace-install.yaml | ||
|
|
||
| 11. Deploy the event-source controller | ||
| NOTE: | ||
| * On GKE, you may need to grant your account the ability to create new custom resource definitions | ||
|
|
||
| kubectl create clusterrolebinding YOURNAME-cluster-admin-binding --clusterrole=cluster-admin [email protected] | ||
| * On Openshift, make sure to grant `anyuid` scc to the service account. | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/base/eventsource-controller/eventsource-controller-deployment.yaml | ||
| 3. Deploy the eventbus, | ||
|
|
||
| 12. Deploy the eventbus. | ||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/examples/eventbus/native.yaml | ||
|
|
||
| kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/examples/eventbus/native.yaml | ||
|
|
||
| ### Using Kustomize | ||
|
|
||
|
|
||