mirror of
https://github.com/kerberos-io/agent.git
synced 2026-08-23 15:08:32 +00:00
few more design tweaks
This commit is contained in:
@@ -111,7 +111,7 @@ We have documented the different deployment models [in the `deployments` directo
|
||||
- [Docker](https://github.com/kerberos-io/agent/tree/master/deployments#1-docker)
|
||||
- [Docker Compose](https://github.com/kerberos-io/agent/tree/master/deployments#2-docker-compose)
|
||||
- [Kubernetes](https://github.com/kerberos-io/agent/tree/master/deployments#3-kubernetes)
|
||||
- [Red Hat OpenShift with Ansible](https://github.com/kerberos-io/agent/tree/master/deployments#4-redhat-ansible-and-openshift)
|
||||
- [Red Hat OpenShift with Ansible](https://github.com/kerberos-io/agent/tree/master/deployments#4-red-hat-ansible-and-openshift)
|
||||
- [Terraform](https://github.com/kerberos-io/agent/tree/master/deployments#5-terraform)
|
||||
- [Salt](https://github.com/kerberos-io/agent/tree/master/deployments#6-salt)
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ We will discuss following deployment models.
|
||||
- [1. Docker](#1-docker)
|
||||
- [2. Docker Compose](#2-docker-compose)
|
||||
- [3. Kubernetes](#3-kubernetes)
|
||||
- [4. RedHat Ansible and OpenShift](#4-redhat-ansible-and-openshift)
|
||||
- [4. Red Hat Ansible and OpenShift](#4-red-hat-ansible-and-openshift)
|
||||
- [5. Kerberos Factory](#5-kerberos-factory)
|
||||
- [6. Terraform](#6-terraform)
|
||||
- [7. Salt](#7-salt)
|
||||
@@ -32,9 +32,9 @@ As described above, `docker` is a great tool for smaller deployments, where you
|
||||
|
||||
> Learn more [about Kerberos Agent in a Kubernetes cluster here](https://github.com/kerberos-io/agent/tree/master/deployments/kubernetes).
|
||||
|
||||
## 4. RedHat Ansible and OpenShift
|
||||
## 4. Red Hat Ansible and OpenShift
|
||||
|
||||
If you running an alternative distribution such as RedHat OpenShift, things will work out exactly as mentioned before with the `Kubernetes` deployment. You'll have all the benefints of RedHat OpenShift on top. One of the things we provide here is an Ansible playbook to deploy the Kerberos Agent in the OpenShift cluster.
|
||||
If you running an alternative distribution such as Red Hat OpenShift, things will work out exactly as mentioned before with the `Kubernetes` deployment. You'll have all the benefints of Red Hat OpenShift on top. One of the things we provide here is an Ansible playbook to deploy the Kerberos Agent in the OpenShift cluster.
|
||||
|
||||
> Learn more [about Kerberos Agent in OpenShift with Ansible](https://github.com/kerberos-io/agent/tree/master/deployments/ansible-openshift).
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Deploy to a RedHat OpenShift cluster with Ansible
|
||||
# Deploy to a Red Hat OpenShift cluster with Ansible
|
||||
|
||||
Kubernetes is great, but you might love OpenShift even more. In this directory you'll find some resources to deploy your Kerberos Agent in an OpenShift cluster using Ansible playbook. We'll review the different tasks of the Ansible playbook step by step; find the complete `playbook.yaml` here.
|
||||
|
||||
@@ -40,6 +40,10 @@ Now you understand what is happening in the playbook, let's run it. Make sure yo
|
||||
|
||||
Specify the `environment` input variable as a `JSON` with all required variables defined in step 1. Reference the `playbook.yml` file and execute.
|
||||
|
||||
ansible-playbook -e '{"oc_cluster_url":"https://api.j5z0adui.westeurope.aroapp.io:6443", "oc_username":"kubeadmin", "oc_password":"xxx"}' playbook.yml
|
||||
ansible-playbook -e '{ \
|
||||
"oc_cluster_url":"https://api.j5z0adui.westeurope.aroapp.io:6443", \
|
||||
"oc_username":"kubeadmin",\
|
||||
"oc_password":"xxx" \
|
||||
}' playbook.yml
|
||||
|
||||
If everything runs as expected you should see you Kerberos Agent deployed, together with an assigned public ip address. Paste the ip address in your browser, the Kerberos Agent web interface will show up. You can use [the default username and password to sign-in](https://github.com/kerberos-io/agent#access-the-kerberos-agent), or if changed to your own (which is recommended).
|
||||
|
||||
Reference in New Issue
Block a user