chronosphere-operator

The Chronosphere Operator is a Kubernetes operator that manages the lifecycle of Chronosphere resources.

Description

The schema for each of these resources matches the chronoctl resource schema. This is done by generating the CRD spec from the Chronosphere API swagger spec. For example manifests, take a look at the config/samples directory.

The Chronosphere Operator currently supports the following resources:

• ChronosphereTeam
• ChronosphereCollection
• ChronosphereDashboard
• ChronosphereClassicDashboard
• ChronosphereMonitor
• ChronosphereNotifier
• ChronosphereNotificationPolicy
• ChronosphereDropRule
• ChronosphereRollupRule
• ChronosphereRecordingRule
• ChronosphereMappingRule
• ChronosphereResourcePools

To monitor the health of the chronosphere-operator, the operator exposes metrics on localhost:8080/metrics which can be scraped by Prometheus. It's recommended to use ServiceMonitor discovery to automatically discover and monitor the chronosphere-operator. A monitoring dashboard for the chronosphere-operator should be deployed with kubectl apply -f assets/Controller-Runtime-Metrics.yaml).

To lock down the generated resources in the Chronosphere UI, set the environment variable UI_LOCK_RESOURCES=true in manager.yaml. This will pass headers to the Chronosphere API which indicate that the resources were created via the chronosphere-operator and cannot be edited in the UI.

Configuration

1. Add base64 encoding to your domain name and API token:

   echo -n "ADDRESS" | base64
   echo -n "API_TOKEN" | base64
   

   Replace the following:

   ADDRESS: your company name prefixed to your Chronosphere Observability Plaftorm instance that ends in .chronosphere.io:443. For example, MY_COMPANY.chronosphere.io:443.

   API_TOKEN: the API token generated from your service account.

2. Copy the values that output to your terminal, which you add as part of your Kubernetes Secret in the next step.

3. In your manager.yaml file in the config/manager directory, locate the Kubernetes Secret and replace values for address and api-token with the encoded values that you copied from your terminal.

Prerequisites

• go version v1.22.0+
• docker version 17.03+.
• kubectl version v1.11.3+.
• Access to a Kubernetes v1.11.3+ cluster.

To Deploy on the cluster

Build and push your image to the location specified by IMG:

make docker-build docker-push IMG=<some-registry>/chronosphere-operator:tag

NOTE: This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permission to the registry if the above commands don’t work.

Install the CRDs into the cluster:

make install

Deploy the Manager to the cluster with the image specified by IMG:

make deploy IMG=<some-registry>/chronosphere-operator:tag

NOTE: If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin.

Create instances of your solution You can apply the samples (examples) from the config/sample:

kubectl apply -k config/samples/

NOTE: Ensure that the samples has default values to test it out.

To Uninstall

Delete the instances (CRs) from the cluster:

kubectl delete -k config/samples/

Delete the APIs(CRDs) from the cluster:

make uninstall

UnDeploy the controller from the cluster:

make undeploy

Project Distribution

Following are the steps to build the installer and distribute this project to users.

1. Build the installer for the image built and published in the registry:

make build-installer IMG=<some-registry>/chronosphere-operator:tag

NOTE: The makefile target mentioned above generates an 'install.yaml' file in the dist directory. This file contains all the resources built with Kustomize, which are necessary to install this project without its dependencies.

2. Using the installer

Users can just run kubectl apply -f to install the project, i.e.:

kubectl apply -f https://raw.githubusercontent.com/<org>/chronosphere-operator/<tag or branch>/dist/install.yaml

Contributing

// TODO(user): Add detailed information on how you would like others to contribute to this project

NOTE: Run make help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation

License

Copyright 2024.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.