To evaluate the services Banzai Cloud One Eye (One Eye) offers, we recommend to create a test environment. This way you can start over any time, and try all the options you are interested in without having to worry about changes made to your existing environment, even if it’s not used in production.

Production installation is very similar, but you must exactly specify which components you want to use.

Prerequisites 🔗︎

Before deploying One Eye on your cluster, complete the following tasks.

Create a test cluster 🔗︎

You need a Kubernetes cluster to test One Eye with. If you don’t already have a Kubernetes cluster to work with, create one with one of the following methods:

  • You can use the Banzai Cloud Pipeline platform to deploy a cluster.
  • Deploy a single-node Banzai Cloud PKE cluster on a physical or virtual Linux box.
  • Launch a cluster at one of the many cloud providers’ managed offerings at their console.
  • Use KinD on your machine (make sure to increase the resource allocation of Docker for Mac).

Create an object store 🔗︎

You will need an object store. Thanos supports many types of object storage, see the official Thanos documentation for details.

Install the One Eye tool 🔗︎

Install the One Eye command-line tool. You can use the One Eye CLI tool to install One Eye and other components to your cluster.

Note: The One Eye CLI supports macOS and Linux (x86_64). It may work on Windows natively, but we don’t test it.

  1. Register for an evaluation version.

    As you might know, Cisco has recently acquired Banzai Cloud. Currently we are in a transitional period and are moving our infrastructure. As part of the process, we are temporarily suspending access to evaluation downloads until we verify that they comply with Cisco’s policies. We hope to resume access to evaluation licenses in April. Until then, contact us so we can discuss your needs and requirements, and organize a live demo.

  2. Install the one-eye-cli package for your environment by running the following command:

    Evaluation downloads are temporarily suspended. Contact us to discuss your needs and requirements, and organize a live demo.

    For other options, see the One Eye CLI Installation Guide.

Set Kubernetes configuration and context 🔗︎

The command-line tool uses your current Kubernetes context, from the file named in the KUBECONFIG environment variable (~/.kube/config by default). Check if this is the cluster you plan to deploy the product by running the following command: kubectl config get-contexts

If there are multiple contexts in the Kubeconfig file, specify the one you want to use with the use-context parameter, for example: kubectl config use-context <context-to-use>

If the cluster is managed by Banzai Cloud Pipeline, complete the following steps. For more detailed instructions, see the Banzai Cloud Pipeline documentation.

  1. Login to your Pipeline instance (for example, by running banzai login --endpoint /pipeline).
  2. Run banzai cluster shell, and select the cluster to use. A subshell with the correct environment will open automatically.

Deploy One Eye 🔗︎

After you have completed the Prerequisites, you can install One Eye on a single cluster.

  1. The following command installs the Logging Operator, the Logging Extension, a Prometheus Operator, and all dependencies.

    one-eye logging install --prometheus

    During the interactive mode, the One Eye CLI will ask for the name of the object storage and the associated secrets.

  2. Wait a few minutes and verify that the components are installed.

    $ kubectl get po
    NAME                                                             READY   STATUS    RESTARTS   AGE
    alertmanager-one-eye-prometheus-operato-alertmanager-0           2/2     Running   0          3m3s
    one-eye-logging-extensions-f8599dd6f-kmd2x                       1/1     Running   0          107s
    one-eye-logging-operator-f7c679745-7dmk5                         1/1     Running   0          114s
    one-eye-prometheus-operato-operator-5d5c4fcfdc-t6lvl             2/2     Running   0          3m15s
    one-eye-prometheus-operator-grafana-76c45c5559-whhlf             2/2     Running   0          3m15s
    one-eye-prometheus-operator-kube-state-metrics-f45595f4c-w5w2z   1/1     Running   0          3m15s
    one-eye-prometheus-operator-prometheus-node-exporter-qplrd       1/1     Running   0          3m15s
    prometheus-one-eye-prometheus-operato-prometheus-0               4/4     Running   1          2m53s

    You should see that the three operators are running.

    To repeat the installation process, just append the one-eye logging install --prometheus --update command.

  3. Configure a simple logging system. Run the following command and follow the on-screen instructions.

    $ one-eye logging configure
    ? Configure persistent volume for buffering logs? No
    kind: Logging
    name: one-eye
    enableRecreateWorkloadOnImmutableFieldChange: true
    controlNamespace: default
    ? Edit the configuration in an editor? No
    ? Apply the configuration? Yes
    observer> resource created name: ...
    ? Create a new Flow? Yes

    The CLI will provide a template for the Logging resource with some basic configuration. You can edit this template and decide to apply it on the cluster or not. After applying the logging resource, continue to create an Output and a Flow.

  4. Configure an S3 output. Run the following command and follow the on-screen instructions. (Currently the interactive mode supports only the S3 output, you can configure other outputs in the Logging operator.)

    $ one-eye logging configure output
    ? What type of output do you need? s3
    ? Select the namespace for your output default
    ? Use the following name for your output s3
    ? S3 Bucket banzai-one-eye
    ? Region of the bucket eu-west-1
    ? Configure authentication based on your current AWS credentials? Yes
    ? Save AKIXXXXXXXXXXXXXXXX to a Kubernetes secret and link it with the output Yes
    # Copyright © 2020 Banzai Cloud
    kind: Output
    name: s3
    namespace: default
    # Reference docs for the output configuration:
        s3_bucket: banzai-one-eye
        s3_region: eu-west-1
        path: logs/${tag}/%Y/%m/%d/
            name: s3-6bcf
            key: awsAccessKeyId
            name: s3-6bcf
            key: awsSecretAccessKey
    ? Edit the configuration in an editor? No
    ? Apply the configuration? Yes
    observer> resource created name: s3...

    If you have your Amazon credential configured in your environment, the CLI will ask if you want to use them to access the bucket. When you choose yes the CLI will automatically create a Kubernetes secret with your Amazon Key and Secret. After specifying the bucket name and region the generated template is ready to be used (or customized). It includes the secret name and bucket information as well.

    Note: For details on configuring different output types, see the Logging Operator quick start guides.

  5. Configure a logging flow. The basic template provides an empty flow. Customize the match section and add filters from the supported filter list.

    $ one-eye logging configure flow
    ? Select the namespace for your flow default
    Available Outputs: [s3]
    ? Select an output s3
    ? Give a name for your flow my-flow
    kind: Flow
    name: my-flow
    namespace: default
    # tag normalizer changes default kubernetes tags coming from fluentbit to the following format: namespace.pod.container
    - tag_normaliser: {}
    # a select without restrictions will forward all events to the outputRefs
    - select: {}
        - s3
    ? Edit the configuration in an editor? No
    ? Apply the configuration? Yes
    observer> resource created name: my-flow...

    After applying the yaml, the logs are flowing to the S3 bucket.

Display the logging flow 🔗︎

In real-life scenarios you have several flows and outputs for different purposes. One Eye helps you review your logging infrastructure by visualizing it. Complete the following steps.

  1. Install the One Eye UI. The following command installs an nginx ingress and the One Eye UI. This ingress is exposed to localhost by default, but you can connect to it via One Eye.

    $ one-eye ingress install --update
  2. Connect to the One Eye Dashboard and review your logging infrastructure.

    one-eye ingress connect

    The One Eye UI opens in your browser. One Eye Dashboard