Skip to content

Latest commit

 

History

History
158 lines (99 loc) · 7.3 KB

CONTRIBUTING.md

File metadata and controls

158 lines (99 loc) · 7.3 KB

How to Contribute to the OpenTelemetry Operator

We'd love your help!

This project is Apache 2.0 licensed and accepts contributions via GitHub pull requests. This document outlines some of the conventions on development workflow, contact points and other resources to make it easier to get your contribution accepted.

We gratefully welcome improvements to documentation as well as to code.

Getting Started

Workflow

It is recommended to follow the "GitHub Workflow". When using GitHub's CLI, here's how it typically looks like:

gh repo fork github.com/open-telemetry/opentelemetry-operator
git checkout -b your-feature-branch
# do your changes
git commit -sam "Add feature X"
gh pr create

Pre-requisites

  • Install Go.
  • Install Kustomize.
  • Have a Kubernetes cluster ready for development. We recommend minikube or kind.

Local run

Build the manifests, install the CRD and run the operator as a local process:

make bundle install run

Deployment with webhooks

When running make run, the webhooks aren't effective as it starts the manager in the local machine instead of in-cluster. To test the webhooks, you'll need to:

  1. configure a proxy between the Kubernetes API server and your host, so that it can contact the webhook in your local machine
  2. create the TLS certificates and place them, by default, on /tmp/k8s-webhook-server/serving-certs/tls.crt. The Kubernetes API server has also to be configured to trust the CA used to generate those certs.

In general, it's just easier to deploy the manager in a Kubernetes cluster instead. For that, you'll need the cert-manager installed. You can install it by running:

make cert-manager

In pursuit of continuous improvement, a variable named CERTMANAGER_VERSION which can be run:

CERTMANAGER_VERSION=1.60 make cert-manager

By default, it will generate an image following the format quay.io/${USER}/opentelemetry-operator:${VERSION}. You can set the following env vars in front of the make command to override parts or the entirety of the image:

  • IMG_PREFIX, to override the registry, namespace and image name (quay.io)
  • USER, to override the namespace
  • IMG_REPO, to override the repository (opentelemetry-operator)
  • VERSION, to override only the version part
  • IMG, to override the entire image specification

Ensure the secret regcred has been created to enable opentelemetry-operator-controller-manager deployment to pull images from your private quay.io registry.

kubectl create secret docker-registry regcred --docker-server=quay.io --docker-username=${USER} --docker-password=${PASSWORD}  -n opentelemetry-operator-system

Alternatively, you could create your repository with Public Visibility.

Once it's ready, the following can be used to build and deploy a manager, along with the required webhook configuration:

make bundle container container-push deploy

Your operator will be available in the opentelemetry-operator-system namespace.

Testing

With an existing cluster (such as minikube), run:

USE_EXISTING_CLUSTER=true make test

Tests can also be run without an existing cluster. For that, install kubebuilder. In this case, the tests will bootstrap etcd and kubernetes-api-server for the tests. Run against an existing cluster whenever possible, though.

End to end tests

To run the end-to-end tests, you'll need kind and kuttl. Refer to their documentation for installation instructions.

Once they are installed, the tests can be executed with make prepare-e2e, which will build an image to use with the tests, followed by make e2e. Each call to the e2e target will setup a fresh kind cluster, making it safe to be executed multiple times with a single prepare-e2e step.

The tests are located under tests/e2e and are written to be used with kuttl. Refer to their documentation to understand how tests are written.

Undeploying the operator from the local cluster

make undeploy

Project Structure

For a general overview of the directories from this operator and what to expect in each one of them, please check out the official GoDoc or the locally-hosted GoDoc

Contributing

Your contribution is welcome! For it to be accepted, we have a few standards that must be followed.

If you are contributing to sync the receivers from otel-collector-contrib, note that the operator only synchronizes receivers that aren't scrapers, as there's no need to open ports in services for this case. In general, receivers would open a UDP/TCP port and the operator should be adding an entry in the Kubernetes Service resource accordingly.

New features

Before starting the development of a new feature, please create an issue and discuss it with the project maintainers. Features should come with documentation and enough tests (unit and/or end-to-end).

Bug fixes

Every bug fix should be accompanied with a unit test, so that we can prevent regressions.

Documentation, typos, ...

They are mostly welcome!

Operator Lifecycle Manager (OLM)

For production environments, it is recommended to use the Operator Lifecycle Manager (OLM) to provision and update the OpenTelemetry Operator. Our operator is available in the Operator Hub, and when making changes involving those manifests the following steps can be used for testing. Refer to the OLM documentation for more complete information.

Setup OLM

When using Kubernetes, install OLM following the official instructions. At the moment of this writing, it involves the following:

operator-sdk olm install

When using OpenShift, the OLM is already installed.

Create the bundle and related images

The following commands will generate a bundle under bundle/, build an image with its contents, build and publish the operator image.

BUNDLE_IMG=docker.io/${USER}/opentelemetry-operator-bundle:latest IMG=docker.io/${USER}/opentelemetry-operator:latest make bundle container container-push bundle-build bundle-push

Install the operator

operator-sdk run bundle docker.io/${USER}/opentelemetry-operator-bundle:latest

Uninstall the operator

The operator can be uninstalled by deleting subscriptions.operators.coreos.com and clusterserviceversion.operators.coreos.com objects from the current namespace.

kubectl delete clusterserviceversion.operators.coreos.com --all
kubectl delete subscriptions.operators.coreos.com --all